[ANN] Bitcredit/CRE - first sidechain, claimable from Bitcoin, pow/pod - page 8.

Destined

member

Activity: 173

Merit: 10

Quote from: MRKLYE on April 16, 2015, 02:47:29 PM

Quote from: Destined on April 16, 2015, 02:33:12 PM

Quote from: MRKLYE on April 16, 2015, 01:12:00 PM

Quote from: Destined on April 16, 2015, 12:06:51 PM

So who has claimed CRE using a bitcoin wallet so far? Was it actually worth the pain of having to start over with a new wallet?

I claimed a small amount to test it, Seemed to work. Far more effective to mine it in my humble opinion.

I sent over your 10 CRE welcome bonus!

Date: 2015-04-16 14:23
To: 1Pt5m2dVKjpRhmNzaic2GhGGeodNGswimd
Debit: -10.00 CRE
Net amount: -10.00 CRE
Transaction ID: d5b3662bbbb86f092412414bf257837fe3b5c685e5d7e2964d95b544099fa419-000

Confirmed, and what was the exchange rate? I seem to be a bit unclear on if it was based on your balance at a set point in time, or if it was based on the cumulative total of deposits into your account by that set point in time.

I believe its based on cumulative total in the address but don't quote me on that though.

CRE is only being traded small scale at the moment, If you look a few pages back you can see the bids/asks.

I should have worded that better but I ment the rate from your btc activity to CRE.

MRKLYE

legendary

Activity: 1358

Merit: 1003

Designer - Developer

Quote from: Destined on April 16, 2015, 02:33:12 PM

Quote from: MRKLYE on April 16, 2015, 01:12:00 PM

Quote from: Destined on April 16, 2015, 12:06:51 PM

So who has claimed CRE using a bitcoin wallet so far? Was it actually worth the pain of having to start over with a new wallet?

I claimed a small amount to test it, Seemed to work. Far more effective to mine it in my humble opinion.

I sent over your 10 CRE welcome bonus!

Date: 2015-04-16 14:23
To: 1Pt5m2dVKjpRhmNzaic2GhGGeodNGswimd
Debit: -10.00 CRE
Net amount: -10.00 CRE
Transaction ID: d5b3662bbbb86f092412414bf257837fe3b5c685e5d7e2964d95b544099fa419-000

Confirmed, and what was the exchange rate? I seem to be a bit unclear on if it was based on your balance at a set point in time, or if it was based on the cumulative total of deposits into your account by that set point in time.

I believe its based on cumulative total in the address but don't quote me on that though.

CRE is only being traded small scale at the moment, If you look a few pages back you can see the bids/asks.

Destined

member

Activity: 173

Merit: 10

Quote from: MRKLYE on April 16, 2015, 01:12:00 PM

Quote from: Destined on April 16, 2015, 12:06:51 PM

So who has claimed CRE using a bitcoin wallet so far? Was it actually worth the pain of having to start over with a new wallet?

I claimed a small amount to test it, Seemed to work. Far more effective to mine it in my humble opinion.

I sent over your 10 CRE welcome bonus!

Date: 2015-04-16 14:23
To: 1Pt5m2dVKjpRhmNzaic2GhGGeodNGswimd
Debit: -10.00 CRE
Net amount: -10.00 CRE
Transaction ID: d5b3662bbbb86f092412414bf257837fe3b5c685e5d7e2964d95b544099fa419-000

Confirmed, and what was the exchange rate? I seem to be a bit unclear on if it was based on your balance at a set point in time, or if it was based on the cumulative total of deposits into your account by that set point in time.

MRKLYE

legendary

Activity: 1358

Merit: 1003

Designer - Developer

Quote from: Destined on April 16, 2015, 12:06:51 PM

So who has claimed CRE using a bitcoin wallet so far? Was it actually worth the pain of having to start over with a new wallet?

I claimed a small amount to test it, Seemed to work. Far more effective to mine it in my humble opinion.

I sent over your 10 CRE welcome bonus!

Date: 2015-04-16 14:23
To: 1Pt5m2dVKjpRhmNzaic2GhGGeodNGswimd
Debit: -10.00 CRE
Net amount: -10.00 CRE
Transaction ID: d5b3662bbbb86f092412414bf257837fe3b5c685e5d7e2964d95b544099fa419-000

Destined

member

Activity: 173

Merit: 10

So who has claimed CRE using a bitcoin wallet so far? Was it actually worth the pain of having to start over with a new wallet?

Gabriel Eiger

sr. member

Activity: 280

Merit: 250

Lead developer of Credits [CRE]

Quote from: gregor12 on April 16, 2015, 07:54:31 AM

My bitcredit chain wont sync (btc chain was fully synced), it stayed at block 6322 or something like that (6 days behind). Once I closed and reopend qt i got error
*** Error moving claim tip. Expected active bitcredit block: 0000000000000000000000000000000000000000000000000000000000000000, was: 0000000013a663baba47abad9d88f5a4bde47e9655c38b2eb474f443093cd019
*** ERROR: Bitcredit: ConnectBlock: Failed to move claim tip to 0000000000000000189a6d0d46b0364748c4c2249ba4a3cbb45db99abcbfd2a9
ERROR: Bitcredit: ConnectTip() : ConnectBlock 000000005fc6f4b75a16b644bc1bd975ec71e7bdfab3144d84915d0efae490d2 failed

edit: I used the block chain file from torrent

Some more info on how to see when you are in sync can be found here:
http://bitcredit-currency.org/viewtopic.php?f=18&t=17

Gabriel Eiger

sr. member

Activity: 280

Merit: 250

Lead developer of Credits [CRE]

Quote from: gregor12 on April 16, 2015, 07:54:31 AM

My bitcredit chain wont sync (btc chain was fully synced), it stayed at block 6322 or something like that (6 days behind). Once I closed and reopend qt i got error
*** Error moving claim tip. Expected active bitcredit block: 0000000000000000000000000000000000000000000000000000000000000000, was: 0000000013a663baba47abad9d88f5a4bde47e9655c38b2eb474f443093cd019
*** ERROR: Bitcredit: ConnectBlock: Failed to move claim tip to 0000000000000000189a6d0d46b0364748c4c2249ba4a3cbb45db99abcbfd2a9
ERROR: Bitcredit: ConnectTip() : ConnectBlock 000000005fc6f4b75a16b644bc1bd975ec71e7bdfab3144d84915d0efae490d2 failed

edit: I used the block chain file from torrent

The fastest way is probably wiping your working directory and restart with a new fresh working directory from the downloaded torrent. I suggest you also look at the log output if the gui appears to be stuck. The interface do not update very well when the Bitcredit chain syncs. Don't forget to backup bitcredit_wallet.dat when you wipe the working directory.

The error message means that you have inconsistency in the state between Bitcoin and Bitcredit. This is normally a non-recoverable error. This error is known and work is being done on handling the problem. Unfortunately it causes some problems for people at the moment. The inconsistency may appear if the Bitcredit-Qt process is killed in the middle of a chainstate update.

Destined

member

Activity: 173

Merit: 10

Quote from: Gabriel Eiger on April 16, 2015, 11:25:35 AM

Quote from: Destined on April 16, 2015, 05:27:30 AM

Quote from: MRKLYE on April 15, 2015, 08:52:50 PM

Quote from: Destined on April 15, 2015, 05:24:29 PM

Quote from: MRKLYE on April 15, 2015, 05:17:18 PM

Quote from: Destined on April 15, 2015, 04:55:32 PM

Quote from: MRKLYE on April 15, 2015, 04:31:50 PM

Quote from: Destined on April 15, 2015, 03:12:21 PM

I am currently having trouble getting the program to run due to bind fail on 0.0.0.0:8333 even when I create a shortcut and specify the -listen=0 flag for it to use any port, it still tries to use 8333, also tried setting things in a bitcredit.conf file with no luck as well.

I'm not exactly an expert on the matter, But it sounds to me like your files in the appdata/roaming/bitcredit directory may be set to read only.
Check it out and see if they are, I recall having a similar issue on one of my first attempts.

Did you use the torrent blockchain method? If so please make sure you fully read and understand the post HERE.

I figured the problem out it was because I had checked out the other one named bitcredits and it was trying to hijack its directory. Or not as while deleting the directory from the other one actually let me pick a directory detecting it was a first run, we quickly resulted back to the other issue.

Also as for the torrent question, no I did not as I already have a full bitcoin block chain and am going to use an alternate method to get the program up to speed, provided it will ever open to create the initial data folders for the blockchain since all it created before it fails to bind is the basic directory structure without the folders for the chains.

I would highly recommend using the Blockchain torrent download as seen HERE.

I tried a few experimental ways and lost a few days mining before Gabriel offered this method which works quite well.

The problem is because its refusing to try and use a port other than 8333 for bitcoin, and I already have a bitcoin client actively running which by design specs wants to use 8333.

I did have a valid Bitcoin-qt install on my computer when I installed Bitcredit but I didn't ever try to run them in unison.
This is a very interesting issue and I'm sure when Gab gets back online he can likely either advise a fix or start coding a patch for the issue.

Hang in there, i had issues in the beginning as well getting it running but Gabriel sorted it out.
I'll hook you up with 10 CRE when you get up and running for the troubles, irregardless of you not being a full member.

Up and running now. 1Pt5m2dVKjpRhmNzaic2GhGGeodNGswimd
Thanks

Good to hear. Did you get the miner started as well?

Yea

Gabriel Eiger

sr. member

Activity: 280

Merit: 250

Lead developer of Credits [CRE]

Quote from: Destined on April 16, 2015, 05:27:30 AM

Quote from: MRKLYE on April 15, 2015, 08:52:50 PM

Quote from: Destined on April 15, 2015, 05:24:29 PM

Quote from: MRKLYE on April 15, 2015, 05:17:18 PM

Quote from: Destined on April 15, 2015, 04:55:32 PM

Quote from: MRKLYE on April 15, 2015, 04:31:50 PM

Quote from: Destined on April 15, 2015, 03:12:21 PM

I am currently having trouble getting the program to run due to bind fail on 0.0.0.0:8333 even when I create a shortcut and specify the -listen=0 flag for it to use any port, it still tries to use 8333, also tried setting things in a bitcredit.conf file with no luck as well.

I'm not exactly an expert on the matter, But it sounds to me like your files in the appdata/roaming/bitcredit directory may be set to read only.
Check it out and see if they are, I recall having a similar issue on one of my first attempts.

Did you use the torrent blockchain method? If so please make sure you fully read and understand the post HERE.

I figured the problem out it was because I had checked out the other one named bitcredits and it was trying to hijack its directory. Or not as while deleting the directory from the other one actually let me pick a directory detecting it was a first run, we quickly resulted back to the other issue.

Also as for the torrent question, no I did not as I already have a full bitcoin block chain and am going to use an alternate method to get the program up to speed, provided it will ever open to create the initial data folders for the blockchain since all it created before it fails to bind is the basic directory structure without the folders for the chains.

I would highly recommend using the Blockchain torrent download as seen HERE.

I tried a few experimental ways and lost a few days mining before Gabriel offered this method which works quite well.

The problem is because its refusing to try and use a port other than 8333 for bitcoin, and I already have a bitcoin client actively running which by design specs wants to use 8333.

I did have a valid Bitcoin-qt install on my computer when I installed Bitcredit but I didn't ever try to run them in unison.
This is a very interesting issue and I'm sure when Gab gets back online he can likely either advise a fix or start coding a patch for the issue.

Hang in there, i had issues in the beginning as well getting it running but Gabriel sorted it out.
I'll hook you up with 10 CRE when you get up and running for the troubles, irregardless of you not being a full member.

Up and running now. 1Pt5m2dVKjpRhmNzaic2GhGGeodNGswimd
Thanks

Good to hear. Did you get the miner started as well?

gregor12

newbie

Activity: 52

Merit: 0

My bitcredit chain wont sync (btc chain was fully synced), it stayed at block 6322 or something like that (6 days behind). Once I closed and reopend qt i got error
*** Error moving claim tip. Expected active bitcredit block: 0000000000000000000000000000000000000000000000000000000000000000, was: 0000000013a663baba47abad9d88f5a4bde47e9655c38b2eb474f443093cd019
*** ERROR: Bitcredit: ConnectBlock: Failed to move claim tip to 0000000000000000189a6d0d46b0364748c4c2249ba4a3cbb45db99abcbfd2a9
ERROR: Bitcredit: ConnectTip() : ConnectBlock 000000005fc6f4b75a16b644bc1bd975ec71e7bdfab3144d84915d0efae490d2 failed

edit: I used the block chain file from torrent

Destined

member

Activity: 173

Merit: 10

Quote from: MRKLYE on April 15, 2015, 08:52:50 PM

Quote from: Destined on April 15, 2015, 05:24:29 PM

Quote from: MRKLYE on April 15, 2015, 05:17:18 PM

Quote from: Destined on April 15, 2015, 04:55:32 PM

Quote from: MRKLYE on April 15, 2015, 04:31:50 PM

Quote from: Destined on April 15, 2015, 03:12:21 PM

I am currently having trouble getting the program to run due to bind fail on 0.0.0.0:8333 even when I create a shortcut and specify the -listen=0 flag for it to use any port, it still tries to use 8333, also tried setting things in a bitcredit.conf file with no luck as well.

I'm not exactly an expert on the matter, But it sounds to me like your files in the appdata/roaming/bitcredit directory may be set to read only.
Check it out and see if they are, I recall having a similar issue on one of my first attempts.

Did you use the torrent blockchain method? If so please make sure you fully read and understand the post HERE.

I figured the problem out it was because I had checked out the other one named bitcredits and it was trying to hijack its directory. Or not as while deleting the directory from the other one actually let me pick a directory detecting it was a first run, we quickly resulted back to the other issue.

Also as for the torrent question, no I did not as I already have a full bitcoin block chain and am going to use an alternate method to get the program up to speed, provided it will ever open to create the initial data folders for the blockchain since all it created before it fails to bind is the basic directory structure without the folders for the chains.

I would highly recommend using the Blockchain torrent download as seen HERE.

I tried a few experimental ways and lost a few days mining before Gabriel offered this method which works quite well.

The problem is because its refusing to try and use a port other than 8333 for bitcoin, and I already have a bitcoin client actively running which by design specs wants to use 8333.

I did have a valid Bitcoin-qt install on my computer when I installed Bitcredit but I didn't ever try to run them in unison.
This is a very interesting issue and I'm sure when Gab gets back online he can likely either advise a fix or start coding a patch for the issue.

Hang in there, i had issues in the beginning as well getting it running but Gabriel sorted it out.
I'll hook you up with 10 CRE when you get up and running for the troubles, irregardless of you not being a full member.

Up and running now. 1Pt5m2dVKjpRhmNzaic2GhGGeodNGswimd
Thanks

Gabriel Eiger

sr. member

Activity: 280

Merit: 250

Lead developer of Credits [CRE]

Quote from: Destined on April 15, 2015, 03:12:21 PM

I am currently having trouble getting the program to run due to bind fail on 0.0.0.0:8333 even when I create a shortcut and specify the -listen=0 flag for it to use any port, it still tries to use 8333, also tried setting things in a bitcredit.conf file with no luck as well.

The bind problem is probably due to that you have a separate Bitcoin client running as well. Bitcredit has a built in Bitcoin client. Try to set the -bitcoin_listen=0 flag. Or change the port with -bitcoin_port=.

Many of the options that options that exist has a "-bitcoin_" for the built in Bitcoin client.

MRKLYE

legendary

Activity: 1358

Merit: 1003

Designer - Developer

Quote from: Destined on April 15, 2015, 05:24:29 PM

Quote from: MRKLYE on April 15, 2015, 05:17:18 PM

Quote from: Destined on April 15, 2015, 04:55:32 PM

Quote from: MRKLYE on April 15, 2015, 04:31:50 PM

Quote from: Destined on April 15, 2015, 03:12:21 PM

I am currently having trouble getting the program to run due to bind fail on 0.0.0.0:8333 even when I create a shortcut and specify the -listen=0 flag for it to use any port, it still tries to use 8333, also tried setting things in a bitcredit.conf file with no luck as well.

I'm not exactly an expert on the matter, But it sounds to me like your files in the appdata/roaming/bitcredit directory may be set to read only.
Check it out and see if they are, I recall having a similar issue on one of my first attempts.

Did you use the torrent blockchain method? If so please make sure you fully read and understand the post HERE.

I figured the problem out it was because I had checked out the other one named bitcredits and it was trying to hijack its directory. Or not as while deleting the directory from the other one actually let me pick a directory detecting it was a first run, we quickly resulted back to the other issue.

Also as for the torrent question, no I did not as I already have a full bitcoin block chain and am going to use an alternate method to get the program up to speed, provided it will ever open to create the initial data folders for the blockchain since all it created before it fails to bind is the basic directory structure without the folders for the chains.

I would highly recommend using the Blockchain torrent download as seen HERE.

I tried a few experimental ways and lost a few days mining before Gabriel offered this method which works quite well.

The problem is because its refusing to try and use a port other than 8333 for bitcoin, and I already have a bitcoin client actively running which by design specs wants to use 8333.

I did have a valid Bitcoin-qt install on my computer when I installed Bitcredit but I didn't ever try to run them in unison.
This is a very interesting issue and I'm sure when Gab gets back online he can likely either advise a fix or start coding a patch for the issue.

Hang in there, i had issues in the beginning as well getting it running but Gabriel sorted it out.
I'll hook you up with 10 CRE when you get up and running for the troubles, irregardless of you not being a full member.

Destined

member

Activity: 173

Merit: 10

Quote from: MRKLYE on April 15, 2015, 05:17:18 PM

Quote from: Destined on April 15, 2015, 04:55:32 PM

Quote from: MRKLYE on April 15, 2015, 04:31:50 PM

Quote from: Destined on April 15, 2015, 03:12:21 PM

I am currently having trouble getting the program to run due to bind fail on 0.0.0.0:8333 even when I create a shortcut and specify the -listen=0 flag for it to use any port, it still tries to use 8333, also tried setting things in a bitcredit.conf file with no luck as well.

I'm not exactly an expert on the matter, But it sounds to me like your files in the appdata/roaming/bitcredit directory may be set to read only.
Check it out and see if they are, I recall having a similar issue on one of my first attempts.

Did you use the torrent blockchain method? If so please make sure you fully read and understand the post HERE.

I figured the problem out it was because I had checked out the other one named bitcredits and it was trying to hijack its directory. Or not as while deleting the directory from the other one actually let me pick a directory detecting it was a first run, we quickly resulted back to the other issue.

Also as for the torrent question, no I did not as I already have a full bitcoin block chain and am going to use an alternate method to get the program up to speed, provided it will ever open to create the initial data folders for the blockchain since all it created before it fails to bind is the basic directory structure without the folders for the chains.

I would highly recommend using the Blockchain torrent download as seen HERE.

I tried a few experimental ways and lost a few days mining before Gabriel offered this method which works quite well.

The problem is because its refusing to try and use a port other than 8333 for bitcoin, and I already have a bitcoin client actively running which by design specs wants to use 8333.

MRKLYE

legendary

Activity: 1358

Merit: 1003

Designer - Developer

Quote from: Destined on April 15, 2015, 04:55:32 PM

Quote from: MRKLYE on April 15, 2015, 04:31:50 PM

Quote from: Destined on April 15, 2015, 03:12:21 PM

I am currently having trouble getting the program to run due to bind fail on 0.0.0.0:8333 even when I create a shortcut and specify the -listen=0 flag for it to use any port, it still tries to use 8333, also tried setting things in a bitcredit.conf file with no luck as well.

I'm not exactly an expert on the matter, But it sounds to me like your files in the appdata/roaming/bitcredit directory may be set to read only.
Check it out and see if they are, I recall having a similar issue on one of my first attempts.

Did you use the torrent blockchain method? If so please make sure you fully read and understand the post HERE.

I figured the problem out it was because I had checked out the other one named bitcredits and it was trying to hijack its directory. Or not as while deleting the directory from the other one actually let me pick a directory detecting it was a first run, we quickly resulted back to the other issue.

Also as for the torrent question, no I did not as I already have a full bitcoin block chain and am going to use an alternate method to get the program up to speed, provided it will ever open to create the initial data folders for the blockchain since all it created before it fails to bind is the basic directory structure without the folders for the chains.

I would highly recommend using the Blockchain torrent download as seen HERE.

I tried a few experimental ways and lost a few days mining before Gabriel offered this method which works quite well.

Destined

member

Activity: 173

Merit: 10

Quote from: MRKLYE on April 15, 2015, 04:31:50 PM

Quote from: Destined on April 15, 2015, 03:12:21 PM

I am currently having trouble getting the program to run due to bind fail on 0.0.0.0:8333 even when I create a shortcut and specify the -listen=0 flag for it to use any port, it still tries to use 8333, also tried setting things in a bitcredit.conf file with no luck as well.

I'm not exactly an expert on the matter, But it sounds to me like your files in the appdata/roaming/bitcredit directory may be set to read only.
Check it out and see if they are, I recall having a similar issue on one of my first attempts.

Did you use the torrent blockchain method? If so please make sure you fully read and understand the post HERE.

I figured the problem out it was because I had checked out the other one named bitcredits and it was trying to hijack its directory. Or not as while deleting the directory from the other one actually let me pick a directory detecting it was a first run, we quickly resulted back to the other issue.

Also as for the torrent question, no I did not as I already have a full bitcoin block chain and am going to use an alternate method to get the program up to speed, provided it will ever open to create the initial data folders for the blockchain since all it created before it fails to bind is the basic directory structure without the folders for the chains.

MRKLYE

legendary

Activity: 1358

Merit: 1003

Designer - Developer

Quote from: Darwerft on April 15, 2015, 04:43:42 PM

Hello Klye Kiss

Got them connections, lets see where this new coin brings us.

Cool

Hail Dar. Let me know when you are downloaded and synced up and I'll send over 10 CRE.
I will make a *tiny* exception to the full member rule as I know you from just-dice.com.

Darwerft

newbie

Activity: 27

Merit: 0

Hello Klye Kiss

Got them connections, lets see where this new coin brings us.

Cool

MRKLYE

legendary

Activity: 1358

Merit: 1003

Designer - Developer

Quote from: Destined on April 15, 2015, 03:12:21 PM

I am currently having trouble getting the program to run due to bind fail on 0.0.0.0:8333 even when I create a shortcut and specify the -listen=0 flag for it to use any port, it still tries to use 8333, also tried setting things in a bitcredit.conf file with no luck as well.

I'm not exactly an expert on the matter, But it sounds to me like your files in the appdata/roaming/bitcredit directory may be set to read only.
Check it out and see if they are, I recall having a similar issue on one of my first attempts.

Did you use the torrent blockchain method? If so please make sure you fully read and understand the post HERE.

Destined

member

Activity: 173

Merit: 10

I am currently having trouble getting the program to run due to bind fail on 0.0.0.0:8333 even when I create a shortcut and specify the -listen=0 flag for it to use any port, it still tries to use 8333, also tried setting things in a bitcredit.conf file with no luck as well.

Topic: [ANN] Bitcredit/CRE - first sidechain, claimable from Bitcoin, pow/pod - page 8. (Read 12967 times)