◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈

[dragos_bdi]

Somebody should talk with Chainz and Bittrex ...

Maybe chains, but bittrex should wait a bit until we confirm payout blocks are working properly

OK.

Just a info. What could throw this error ?

 

Code:

bitcreditd: main.cpp:3811: void ProcessGetData(CNode*): Assertion `!"cannot load block from disk"' failed.

Likely a corruption of the block data

redownloaded the whole blockchain. let's see if it will dump again ...
thx

[sawa]

For synchronization to be correct I made this config in bitcredit.conf:

Code:

rpcuser=(leave old)
...
port=(It's necessary to set any free port, but not 8877. The port number must be different from previous. It is for wallets with the wrong blockchain not connected to your wallet as they remember your previous IP and p2p port)
irc=0
connect=41.191.238.189
connect=82.211.1.181:8877
connect=91.230.123.101:8877

- connect, but not addnode. This method does not give the wallet to exchange nodes, it will only connect to the specified nodes.
Make a backup file of wallet.dat
Before starting a wallet from a directory with blockchain delete all files except bitcredit.conf and wallet.dat.
Run wallet and wait until the full synchronization will be finished.

[bitcreditscc]

For synchronization to be correct I made this config in bitcredit.conf:

Code:

rpcuser=(leave old)
...
port=(It's necessary to set any free port, but not 8877. The port number must be different from previous. It is for wallets with the wrong blockchain not connected to your wallet as they remember your previous IP and p2p port)
irc=0
connect=41.191.238.189
connect=82.211.1.181:8877
connect=91.230.123.101:8877

- connect, but not addnode. This method does not give the wallet to exchange nodes, it will only connect to the specified nodes.
Make a backup file of wallet.dat
Before starting a wallet from a directory with blockchain delete all files except bitcredit.conf and wallet.dat.
Run wallet and wait until the full synchronization will be finished.

Unless we can find someone to modify p2pool code to create payouts , then p2pool blocks will be invalid after next update.

[thelonecrouton]

When's the next superblock? Chainz has the last one at 200700, but maybe that's beed forked off, was there one at 201600, and the next one at 202500?

I submitted another test bid earlier this afternoon ( http://explorer.dashpay.io/address/Xypcx2iE8rCtC3tjw5M8sxpRzn4JuoSaBH ) and right now there are no other new BTC/LTC bids so unless someone else ponies up I expect to get a big pile of BCR.  

[sawa]

For synchronization to be correct I made this config in bitcredit.conf:

Code:

rpcuser=(leave old)
...
port=(It's necessary to set any free port, but not 8877. The port number must be different from previous. It is for wallets with the wrong blockchain not connected to your wallet as they remember your previous IP and p2p port)
irc=0
connect=41.191.238.189
connect=82.211.1.181:8877
connect=91.230.123.101:8877

- connect, but not addnode. This method does not give the wallet to exchange nodes, it will only connect to the specified nodes.
Make a backup file of wallet.dat
Before starting a wallet from a directory with blockchain delete all files except bitcredit.conf and wallet.dat.
Run wallet and wait until the full synchronization will be finished.

Unless we can find someone to modify p2pool code to create payouts , then p2pool blocks will be invalid after next update.

Probably first you need to completely restore the blockchain, block explorer and exchanges.
And only then think about p2pool.
I am sure you will succeed.

[bitcreditscc]

When's the next superblock? Chainz has the last one at 200700, but maybe that's beed forked off, was there one at 201600, and the next one at 202500?

I submitted another test bid earlier this afternoon ( http://explorer.dashpay.io/address/Xypcx2iE8rCtC3tjw5M8sxpRzn4JuoSaBH ) and right now there are no other new BTC/LTC bids so unless someone else ponies up I expect to get a big pile of BCR.  

all your bids now appear in the bid file. i want to improve the code we are using there to avoid the errors hack jumped by catching. It has to be done using json to make things clean. it will do for now, but that's definitely high on the to-do list.

yes 202500 is the next payout block and that is why i am none too happy about sawa re-introducing a pool before we have verified that this part works. pool blocks are still accepted, but we may have to change this in order to bring everyone on to the same page.

if block 202500 does not payout properly, i will hard fork @ 202499 to ensure that it does and so do the next payout blocks. This is why i said the exchange should wait until we have everything in order.

For synchronization to be correct I made this config in bitcredit.conf:

Code:

rpcuser=(leave old)
...
port=(It's necessary to set any free port, but not 8877. The port number must be different from previous. It is for wallets with the wrong blockchain not connected to your wallet as they remember your previous IP and p2p port)
irc=0
connect=41.191.238.189
connect=82.211.1.181:8877
connect=91.230.123.101:8877

- connect, but not addnode. This method does not give the wallet to exchange nodes, it will only connect to the specified nodes.
Make a backup file of wallet.dat
Before starting a wallet from a directory with blockchain delete all files except bitcredit.conf and wallet.dat.
Run wallet and wait until the full synchronization will be finished.

Unless we can find someone to modify p2pool code to create payouts , then p2pool blocks will be invalid after next update.

Probably first you need to completely restore the blockchain, block explorer and exchanges.
And only then think about p2pool.
I am sure you will succeed.

Actually it's the other way round, it's pool, then block explorer and finally exchange.

[dbt1033]

Are AMD or NVIDIA cards better for momentum algo?

I want to build a BCR rig...

Any suggestions welcome.

I was thinking this would crush it...  8gb of gddr5  http://www.newegg.com/Product/Product.aspx?Item=N82E16814202147

[thelonecrouton]

Are AMD or NVIDIA cards better for momentum algo?

I want to build a BCR rig...

Any suggestions welcome.

I was thinking this would crush it...  8gb of gddr5  http://www.newegg.com/Product/Product.aspx?Item=N82E16814202147

BCR is moving to low-wattage BN only mining to eliminate the kind of waste you are proposing!

Better to invest in or bid for some BCR instead and earn service rewards for running a Banknode, while also backing the currency.


Bidding addresses are as follows, bid as much or as little as you please, current bids may be found in the bidtracker directory, although they will soon be updated and shown in the wallet...

BTC: 16f5dJd4EHRrQwGGRMczA69qbJYs4msBQ5
LTC: Lc7ebfQPz6VJ8qmXYaaFxBYLpDz2XsDu7c
DASH: Xypcx2iE8rCtC3tjw5M8sxpRzn4JuoSaBH
(you can verify these addresses in bidtracker.cpp - https://github.com/bitcreditscc/bicreditsnew/blob/master/src/bidtracker.cpp)

You get a proportional chunk of the 30000 BCR minted each superblock, every 900 blocks (appx. once a day.)

For the cost of that GPU (never mind the running costs) you could own 6 or 7 Banknodes.

[dbt1033]

Are AMD or NVIDIA cards better for momentum algo?

I want to build a BCR rig...

Any suggestions welcome.

I was thinking this would crush it...  8gb of gddr5  http://www.newegg.com/Product/Product.aspx?Item=N82E16814202147

BCR is moving to low-wattage BN only mining to eliminate the kind of waste you are proposing!

Better to invest in or bid for some BCR instead and earn service rewards for running a Banknode, while also backing the currency.


Bidding addresses are as follows, bid as much or as little as you please, current bids may be found in the bidtracker directory, although they will soon be updated and shown in the wallet...

BTC: 16f5dJd4EHRrQwGGRMczA69qbJYs4msBQ5
LTC: Lc7ebfQPz6VJ8qmXYaaFxBYLpDz2XsDu7c
DASH: Xypcx2iE8rCtC3tjw5M8sxpRzn4JuoSaBH
(you can verify these addresses in bidtracker.cpp - https://github.com/bitcreditscc/bicreditsnew/blob/master/src/bidtracker.cpp)

You get a proportional chunk of the 30000 BCR minted each superblock, every 900 blocks (appx. once a day.)

Good to see you crouton!  I was reading about this...  but didn't really understand until you explained it.

I used to have hundreds of thousands of BCR... but sent most of it to an address that I didn't have a private key for...

I've been buying back in slowly, will probably have a bank node up in a month or two.  Keep selling it cheap guys

Hey, I'm a consumer...wasting is what I do

[jasemoney]

Are AMD or NVIDIA cards better for momentum algo?

I want to build a BCR rig...

Any suggestions welcome.

I was thinking this would crush it...  8gb of gddr5  http://www.newegg.com/Product/Product.aspx?Item=N82E16814202147

BCR is moving to low-wattage BN only mining to eliminate the kind of waste you are proposing!

Better to invest in or bid for some BCR instead and earn service rewards for running a Banknode, while also backing the currency.


Bidding addresses are as follows, bid as much or as little as you please, current bids may be found in the bidtracker directory, although they will soon be updated and shown in the wallet...

BTC: 16f5dJd4EHRrQwGGRMczA69qbJYs4msBQ5
LTC: Lc7ebfQPz6VJ8qmXYaaFxBYLpDz2XsDu7c
DASH: Xypcx2iE8rCtC3tjw5M8sxpRzn4JuoSaBH
(you can verify these addresses in bidtracker.cpp - https://github.com/bitcreditscc/bicreditsnew/blob/master/src/bidtracker.cpp)

You get a proportional chunk of the 30000 BCR minted each superblock, every 900 blocks (appx. once a day.)

For the cost of that GPU (never mind the running costs) you could own 6 or 7 Banknodes.

Proportional chunk is great, I thought it's highest bidder wins but I haven't been paying to close attention. How does the payout base the proportion of differently priced btc, dash, ltc? Is there anything special needed to bid aside from pay those addresses? If there isn't a bid writeup can someone provide or link?
As a side note on those addresses..
BTC .001
Ltc .0299
Dash .31
Seems like a steal :p

[thelonecrouton]

Proportional chunk is great, I thought it's highest bidder wins but I haven't been paying to close attention. How does the payout base the proportion of differently priced btc, dash, ltc?

LTC and DASH are converted to their BTC value and it gets calculated from there.

Is there anything special needed to bid aside from pay those addresses? If there isn't a bid writeup can someone provide or link?
As a side note on those addresses..
BTC .001
Ltc .0299
Dash .31
Seems like a steal :p

I'm just sending some test bids, I'm unclear yet on the exact redemption process but when I've seen how the whole thing works I'll be working on in-wallet GUI streamlining of things.

[fishbone]

Supposed to run with "setgenerate true" on the banknode wallets?

[bitcreditscc]

Proportional chunk is great, I thought it's highest bidder wins but I haven't been paying to close attention. How does the payout base the proportion of differently priced btc, dash, ltc?

LTC and DASH are converted to their BTC value and it gets calculated from there.

Is there anything special needed to bid aside from pay those addresses? If there isn't a bid writeup can someone provide or link?
As a side note on those addresses..
BTC .001
Ltc .0299
Dash .31
Seems like a steal :p

I'm just sending some test bids, I'm unclear yet on the exact redemption process but when I've seen how the whole thing works I'll be working on in-wallet GUI streamlining of things.

Basics

When you send a bid, the bid tracker does a look up of the address you sent from, and then allocates the coins to that address converted to BCR address format.

So , when you want to redeem, you simply import the privkey of the address you used to send, and your coins should be there.

Minimum bids should be equivalent to 0.001 (going to make this mandatory and ignore all smaller bids as they f** up calculations) Coinbase tx is very finnicky and should be exact or getblocktemplate will fail.

[bitcreditscc]

ok, so we have two oprions, let the chain continue as is and issue an update that fixes things in a day or two or else halt the chain hard fork @ 202499 and proceed.

I'm all for the first option i';d like to start maintaining a policy of updates on the run, instead of halting. The update is going to do the following

1) Place checks against blocks to ensure that BN payments and Payouts are made
2) Activate IX
3) Ensure BN only mining (you can use a pool BN to mine if the owner is willing to share his key with you)
4) (Maybe) institute block # limits on BNs (this will result in 3 being invalidated and make the chain solo mining only

[thelonecrouton]

When you send a bid, the bid tracker does a look up of the address you sent from, and then allocates the coins to that address converted to BCR address format.

So , when you want to redeem, you simply import the privkey of the address you used to send, and your coins should be there.

Not working for me, or I'm doing something wrong.

I unlocked my DASH wallet, ran 'dumpprivkey <address-I-bid-from>', then unlocked my BCR wallet and ran 'importprivkey <privkey-for-DASH-address>' and got

Invalid private key encoding (code -5)

[jasemoney]

Proportional chunk is great, I thought it's highest bidder wins but I haven't been paying to close attention. How does the payout base the proportion of differently priced btc, dash, ltc?

LTC and DASH are converted to their BTC value and it gets calculated from there.

Is there anything special needed to bid aside from pay those addresses? If there isn't a bid writeup can someone provide or link?
As a side note on those addresses..
BTC .001
Ltc .0299
Dash .31
Seems like a steal :p

I'm just sending some test bids, I'm unclear yet on the exact redemption process but when I've seen how the whole thing works I'll be working on in-wallet GUI streamlining of things.

Basics

When you send a bid, the bid tracker does a look up of the address you sent from, and then allocates the coins to that address converted to BCR address format.

So , when you want to redeem, you simply import the privkey of the address you used to send, and your coins should be there.

Minimum bids should be equivalent to 0.001 (going to make this mandatory and ignore all smaller bids as they f** up calculations) Coinbase tx is very finnicky and should be exact or getblocktemplate will fail.

Maybe this has been discussed, what happens if I'm dumb and send from exchange or anywhere I don't control the privkey. Most people don't run full nodes and spv keys are different than full privkeys. How much would it suck to change it to just have the bitcredits client generate a receiving address based on coin type either by a new address or building off a privkey you already use to recieve bitcredits. In this way no matter where you sent from you could be credited.
Possibly The setup currently of sending to 1 address to bid would have to be reworked for this to work.. or have the bitcredits client register personal addresses to recieve btc ltc dash. And create a workflow to bid from your balance that way inside the wallet.

[bitcreditscc]

When you send a bid, the bid tracker does a look up of the address you sent from, and then allocates the coins to that address converted to BCR address format.

So , when you want to redeem, you simply import the privkey of the address you used to send, and your coins should be there.

Not working for me, or I'm doing something wrong.

I unlocked my DASH wallet, ran 'dumpprivkey <address-I-bid-from>', then unlocked my BCR wallet and ran 'importprivkey <privkey-for-DASH-address>' and got

Invalid private key encoding (code -5)

ok, likely i missed key conversion number, will look at that now. i'm already working off 0.30.17.1 now so ya'll can expect news in time.

[bitcreditscc]

Proportional chunk is great, I thought it's highest bidder wins but I haven't been paying to close attention. How does the payout base the proportion of differently priced btc, dash, ltc?

LTC and DASH are converted to their BTC value and it gets calculated from there.

Is there anything special needed to bid aside from pay those addresses? If there isn't a bid writeup can someone provide or link?
As a side note on those addresses..
BTC .001
Ltc .0299
Dash .31
Seems like a steal :p

I'm just sending some test bids, I'm unclear yet on the exact redemption process but when I've seen how the whole thing works I'll be working on in-wallet GUI streamlining of things.

Basics

When you send a bid, the bid tracker does a look up of the address you sent from, and then allocates the coins to that address converted to BCR address format.

So , when you want to redeem, you simply import the privkey of the address you used to send, and your coins should be there.

Minimum bids should be equivalent to 0.001 (going to make this mandatory and ignore all smaller bids as they f** up calculations) Coinbase tx is very finnicky and should be exact or getblocktemplate will fail.

Maybe this has been discussed, what happens if I'm dumb and send from exchange or anywhere I don't control the privkey. Most people don't run full nodes and spv keys are different than full privkeys. How much would it suck to change it to just have the bitcredits client generate a receiving address based on coin type either by a new address or building off a privkey you already use to recieve bitcredits. In this way no matter where you sent from you could be credited.
Possibly The setup currently of sending to 1 address to bid would have to be reworked for this to work.. or have the bitcredits client register personal addresses to recieve btc ltc dash. And create a workflow to bid from your balance that way inside the wallet.

Well the problem is consensus, if every node was producing it's own bidding address, it would be extremely difficult to get consensus unless we changed the bids from any amount you want (above the minimum), to a very specific sequence(s) which is far more prone to problems.

You are right about spv keys and i am working on a rpc method to convert any type of key into a standard BCR key.

You would not believe if you saw the full to-do list 

[jasemoney]

Proportional chunk is great, I thought it's highest bidder wins but I haven't been paying to close attention. How does the payout base the proportion of differently priced btc, dash, ltc?

LTC and DASH are converted to their BTC value and it gets calculated from there.

Is there anything special needed to bid aside from pay those addresses? If there isn't a bid writeup can someone provide or link?
As a side note on those addresses..
BTC .001
Ltc .0299
Dash .31
Seems like a steal :p

I'm just sending some test bids, I'm unclear yet on the exact redemption process but when I've seen how the whole thing works I'll be working on in-wallet GUI streamlining of things.

Basics

When you send a bid, the bid tracker does a look up of the address you sent from, and then allocates the coins to that address converted to BCR address format.

So , when you want to redeem, you simply import the privkey of the address you used to send, and your coins should be there.

Minimum bids should be equivalent to 0.001 (going to make this mandatory and ignore all smaller bids as they f** up calculations) Coinbase tx is very finnicky and should be exact or getblocktemplate will fail.

Maybe this has been discussed, what happens if I'm dumb and send from exchange or anywhere I don't control the privkey. Most people don't run full nodes and spv keys are different than full privkeys. How much would it suck to change it to just have the bitcredits client generate a receiving address based on coin type either by a new address or building off a privkey you already use to recieve bitcredits. In this way no matter where you sent from you could be credited.
Possibly The setup currently of sending to 1 address to bid would have to be reworked for this to work.. or have the bitcredits client register personal addresses to recieve btc ltc dash. And create a workflow to bid from your balance that way inside the wallet.

Well the problem is consensus, if every node was producing it's own bidding address, it would be extremely difficult to get consensus unless we changed the bids from any amount you want (above the minimum), to a very specific sequence(s) which is far more prone to problems.

You are right about spv keys and i am working on a rpc method to convert any type of key into a standard BCR key.

You would not believe if you saw the full to-do list  

My goodness I'm sure it's huge. Thanks for the info. And I'll have access to my desktop again tomorrow I've been away for weeks, will be able to do builds and run some mining to help either as a banknode cpu only or gpu as needed.

[bitcreditscc]

Proportional chunk is great, I thought it's highest bidder wins but I haven't been paying to close attention. How does the payout base the proportion of differently priced btc, dash, ltc?

LTC and DASH are converted to their BTC value and it gets calculated from there.

Is there anything special needed to bid aside from pay those addresses? If there isn't a bid writeup can someone provide or link?
As a side note on those addresses..
BTC .001
Ltc .0299
Dash .31
Seems like a steal :p

I'm just sending some test bids, I'm unclear yet on the exact redemption process but when I've seen how the whole thing works I'll be working on in-wallet GUI streamlining of things.

Basics

When you send a bid, the bid tracker does a look up of the address you sent from, and then allocates the coins to that address converted to BCR address format.

So , when you want to redeem, you simply import the privkey of the address you used to send, and your coins should be there.

Minimum bids should be equivalent to 0.001 (going to make this mandatory and ignore all smaller bids as they f** up calculations) Coinbase tx is very finnicky and should be exact or getblocktemplate will fail.

Maybe this has been discussed, what happens if I'm dumb and send from exchange or anywhere I don't control the privkey. Most people don't run full nodes and spv keys are different than full privkeys. How much would it suck to change it to just have the bitcredits client generate a receiving address based on coin type either by a new address or building off a privkey you already use to recieve bitcredits. In this way no matter where you sent from you could be credited.
Possibly The setup currently of sending to 1 address to bid would have to be reworked for this to work.. or have the bitcredits client register personal addresses to recieve btc ltc dash. And create a workflow to bid from your balance that way inside the wallet.

Well the problem is consensus, if every node was producing it's own bidding address, it would be extremely difficult to get consensus unless we changed the bids from any amount you want (above the minimum), to a very specific sequence(s) which is far more prone to problems.

You are right about spv keys and i am working on a rpc method to convert any type of key into a standard BCR key.

You would not believe if you saw the full to-do list  

My goodness I'm sure it's huge. Thanks for the info. And I'll have access to my desktop again tomorrow I've been away for weeks, will be able to do builds and run some mining to help either as a banknode cpu only or gpu as needed.

Great!! thanks, i appreciate all the help i can get.

While the list is dizzying...i find it inspiring, it means there is always room for improvement.