sorry for your lost.. man who said LOL to me..
Topic: ◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈ - page 104. (Read 284526 times)
for the next two days i will not be saying much, please understand i need tine to finish ironing out the issues. Right now the chain is ok, but someone has been trying their damn best to shut us down. From DDoS to constantly trying to fork the chain. The last two forks were a result of someone slamming the network with a ahit ton of hash, then dropping off... then doing it again.
You can see the evidence it you use "getchaintips"typical brnachlen is supposed to 1, but whoever it is managed to get three of len> 3.
Also if you have noticed, there's over 800 nodes running the old wallet version that just popped up out of nowhere.
Not sure if it's someone who has something against us or if soeone is trying to show me the loopholes in current design, but i will respond, i just need a few more hours of tie to figure out one key issue.
see:- we want to prevent miners from producing consecutive blocks , this will effectively remove non-beneficial competition. Then we also want to restrict mining to BNs only.
This is done by maintaining a blockmap of the last 5 blocks , which at every new block we check out and see if the coinbase scriptpubkey matches any in the map, if it does, then it is invalid as that Bn is not authorized to produce another block yet.
I know it seems very tedious, but it actually is the way forward to building a scalable non-exclusionary distribution system that will support infrastructure like BAnking and Insurance.
Can you imagine trying to run that type of network if every miner needed a warehouse of hardware to keep up? How would a new comer get into the system without having to spend millions on hardware?
Would it make sense for a Bn owner of a small company to have to make the same investment as a multi-national corp?
i'm around.....just have my head buried somewhere deep in the code.
You can see the evidence it you use "getchaintips"typical brnachlen is supposed to 1, but whoever it is managed to get three of len> 3.
Also if you have noticed, there's over 800 nodes running the old wallet version that just popped up out of nowhere.
Not sure if it's someone who has something against us or if soeone is trying to show me the loopholes in current design, but i will respond, i just need a few more hours of tie to figure out one key issue.
see:- we want to prevent miners from producing consecutive blocks , this will effectively remove non-beneficial competition. Then we also want to restrict mining to BNs only.
This is done by maintaining a blockmap of the last 5 blocks , which at every new block we check out and see if the coinbase scriptpubkey matches any in the map, if it does, then it is invalid as that Bn is not authorized to produce another block yet.
I know it seems very tedious, but it actually is the way forward to building a scalable non-exclusionary distribution system that will support infrastructure like BAnking and Insurance.
Can you imagine trying to run that type of network if every miner needed a warehouse of hardware to keep up? How would a new comer get into the system without having to spend millions on hardware?
Would it make sense for a Bn owner of a small company to have to make the same investment as a multi-national corp?
i'm around.....just have my head buried somewhere deep in the code.
I had not seen the updated ann with the bidding explained. It says the proceeds of this auction is sent to a multisig address and the effect is immediately felt on the bcr ecosystem. Can you explain how that affects the BCR ecosystem? how are these "bid funds" used?
Instead of distribution only to miners, who spend lots of money on mining hardware and electricity bills, BCR is distributed directly to anyone who bids for it. The money that miners would have spent lining the pockets of hardware and utility companies goes directly to backing BCR instead.
Initially it's BTC/LTC/DASH that will be held as assets, jointly owned by everyone with BCR, and administered when needed by a quorum (currently it's a 3-of-5 multisig setup) of BN owners. There will follow bidding via fiat currency gateways too.
Personally I'd like to see most of the BTC/LTC/DASH/fiat converted to PMs - ASAP, because I frankly see no future for any fiat or cryptofiat currency backed by nothing but speculation and hot air - and held secure by companies that specialise in that, with, again, those reserves being accessible only via a quorum of BN owners.
BCR will have it's own voting system too, so all holders will have a say, probably proportional to their BCR balance.
Thanks.
What do you mean by PMs?
Over half of this BCRs went to one of my Banknode wallets and yesterday I already mentioned it to one of our members but didn't get any explanation. So far I didn't bid anything so how it works ? And what's with "nulldata" address ?
Yeah, there are some kinks still to be worked out. The dev and team are on the case.
I had not seen the updated ann with the bidding explained. It says the proceeds of this auction is sent to a multisig address and the effect is immediately felt on the bcr ecosystem. Can you explain how that affects the BCR ecosystem? how are these "bid funds" used?
Instead of distribution only to miners, who spend lots of money on mining hardware and electricity bills, BCR is distributed directly to anyone who bids for it. The money that miners would have spent lining the pockets of hardware and utility companies goes directly to backing BCR instead.
Initially it's BTC/LTC/DASH that will be held as assets, jointly owned by everyone with BCR, and administered when needed by a quorum (currently it's a 3-of-5 multisig setup) of BN owners. There will follow bidding via fiat currency gateways too.
Personally I'd like to see most of the BTC/LTC/DASH/fiat converted to PMs - ASAP, because I frankly see no future for any fiat or cryptofiat currency backed by nothing but speculation and hot air - and held secure by companies that specialise in that, with, again, those reserves being accessible only via a quorum of BN owners.
BCR will have it's own voting system too, so all holders will have a say, probably proportional to their BCR balance.
Every 900 blocks (appx. once a day) there's a superblock, to distribute the day's newly minted BCR to whoever has bid for it.
Soon all tx validation will be moved to BNs only.
'Mining' is being axed as a distribution mechanism in favour of a less exclusionary bidding system, where anyone can acquire fresh BCR, not just geeks with fancy hardware (and parents to pay the electricity bills.)
Over half of this BCRs went to one of my Banknode wallets and yesterday I already mentioned it to one of our members but didn't get any explanation. So far I didn't bid anything so how it works ? And what's with "nulldata" address ?
Every 900 blocks (appx. once a day) there's a superblock, to distribute the day's newly minted BCR to whoever has bid for it.
Soon all tx validation will be moved to BNs only.
'Mining' is being axed as a distribution mechanism in favour of a less exclusionary bidding system, where anyone can acquire fresh BCR, not just geeks with fancy hardware (and parents to pay the electricity bills.)
I had not seen the updated ann with the bidding explained. It says the proceeds of this auction is sent to a multisig address and the effect is immediately felt on the bcr ecosystem. Can you explain how that affects the BCR ecosystem? how are these "bid funds" used?
**EDIT**
Also, It would be nice to get a status update on the crashing wallet issue... my nodes have been offline for a week now.....
Every 900 blocks (appx. once a day) there's a superblock, to distribute the day's newly minted BCR to whoever has bid for it.
Aha OK. But somebody have problem with sync. I cant sync wallet. Blocked at 200740 now
Every 900 blocks (appx. once a day) there's a superblock, to distribute the day's newly minted BCR to whoever has bid for it.
Soon all tx validation will be moved to BNs only.
'Mining' is being axed as a distribution mechanism in favour of a less exclusionary bidding system, where anyone can acquire fresh BCR, not just geeks with fancy hardware (and parents to pay the electricity bills.)
I re-sync the wallet RC 5. I have got blocked at 200 729 with two peers.
I see the peers gives correct block number but further than 200729 client doesn't go
Quote

{
"version" : 301609,
"protocolversion" : 70009,
"walletversion" : 60000,
"balance" : 54429.57838104,
"darksend_balance" : 0.00000000,
"blocks" : 200729,
"timeoffset" : 0,
"moneysupply" : 19637420.99810297,
"connections" : 2,
"proxy" : "",
"difficulty" : 0.00000397,
"testnet" : false,
"keypoololdest" : 1441537704,
"keypoolsize" : 2,
"unlocked_until" : 0,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
{
"version" : 301609,
"protocolversion" : 70009,
"walletversion" : 60000,
"balance" : 54429.57838104,
"darksend_balance" : 0.00000000,
"blocks" : 200729,
"timeoffset" : 0,
"moneysupply" : 19637420.99810297,
"connections" : 2,
"proxy" : "",
"difficulty" : 0.00000397,
"testnet" : false,
"keypoololdest" : 1441537704,
"keypoolsize" : 2,
"unlocked_until" : 0,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
Quote

[
{
"id" : 1,
"addr" : "62.108.35.172:8877",
"addrlocal" : "109.93.182.151:21822",
"services" : "0000000000000001",
"lastsend" : 1441630057,
"lastrecv" : 1441630058,
"bytessent" : 21680,
"bytesrecv" : 12110,
"conntime" : 1441629811,
"pingtime" : 0.14601900,
"version" : 70009,
"subver" : "/Section 32:0.30.16.9/",
"inbound" : false,
"startingheight" : 201537,
"banscore" : 0,
"servicesdesc" : "MSG RELAY ASSETS ESCROW IBTP BANK BRIDGE",
"synced_headers" : 201537,
"synced_blocks" : 200729,
"inflight" : [
],
"whitelisted" : false
},
{
"id" : 2,
"addr" : "82.200.205.30:8877",
"addrlocal" : "109.93.182.151:21841",
"services" : "0000000000000001",
"lastsend" : 1441630059,
"lastrecv" : 1441630059,
"bytessent" : 21680,
"bytesrecv" : 12136,
"conntime" : 1441629813,
"pingtime" : 0.18802300,
"version" : 70009,
"subver" : "/Section 32:0.30.16.9/",
"inbound" : false,
"startingheight" : 201537,
"banscore" : 0,
"servicesdesc" : "MSG RELAY ASSETS ESCROW IBTP BANK BRIDGE",
"synced_headers" : 201537,
"synced_blocks" : 200729,
"inflight" : [
],
"whitelisted" : false
}
]
[
{
"id" : 1,
"addr" : "62.108.35.172:8877",
"addrlocal" : "109.93.182.151:21822",
"services" : "0000000000000001",
"lastsend" : 1441630057,
"lastrecv" : 1441630058,
"bytessent" : 21680,
"bytesrecv" : 12110,
"conntime" : 1441629811,
"pingtime" : 0.14601900,
"version" : 70009,
"subver" : "/Section 32:0.30.16.9/",
"inbound" : false,
"startingheight" : 201537,
"banscore" : 0,
"servicesdesc" : "MSG RELAY ASSETS ESCROW IBTP BANK BRIDGE",
"synced_headers" : 201537,
"synced_blocks" : 200729,
"inflight" : [
],
"whitelisted" : false
},
{
"id" : 2,
"addr" : "82.200.205.30:8877",
"addrlocal" : "109.93.182.151:21841",
"services" : "0000000000000001",
"lastsend" : 1441630059,
"lastrecv" : 1441630059,
"bytessent" : 21680,
"bytesrecv" : 12136,
"conntime" : 1441629813,
"pingtime" : 0.18802300,
"version" : 70009,
"subver" : "/Section 32:0.30.16.9/",
"inbound" : false,
"startingheight" : 201537,
"banscore" : 0,
"servicesdesc" : "MSG RELAY ASSETS ESCROW IBTP BANK BRIDGE",
"synced_headers" : 201537,
"synced_blocks" : 200729,
"inflight" : [
],
"whitelisted" : false
}
]
I see the peers gives correct block number but further than 200729 client doesn't go
Sawa , can you check the time on your server? seems there is a 6 hour short fall somewhere and i can't find it on our side. Meanwhile, everyone who is upgrading, please YOU MUST RE-SYNC. Many peers are still broadcasting invalid blocks because they did not re-sync since we passed block 199999.
Please ensure you re-sync and are using 0.30.16.9 (or 0.30.17.0 for devs and testing) with 70009
I think we need to fast track the move to BN only mining because noone has managed to modify the p2pool code to handle the bidding process.
DATE/TIME is correct, timezone too. ntp daemon takes time from several ntp servers.Please ensure you re-sync and are using 0.30.16.9 (or 0.30.17.0 for devs and testing) with 70009
I think we need to fast track the move to BN only mining because noone has managed to modify the p2pool code to handle the bidding process.
In addition, more work pieces 30 different coin wallets without problems and a dozen nodes p2ools.
Latest version of the wallet from https://github.com/bitcreditscc/bicreditsnew.git
Quote
/usr/local/src/bicreditsnew# git pull
Already up-to-date.
Already up-to-date.
I deleted all the files except wallet.dat and bitcredit.conf and loaded blokchain again.
Quote
# bitcredit-cli getinfo
{
"version" : 301609,
"protocolversion" : 70009,
"walletversion" : 60000,
"balance" :
"darksend_balance" : 0.00000000,
"blocks" : 201385,
"timeoffset" : 0,
"moneysupply" : 19649228.99810293,
"connections" : 13,
"proxy" : "",
"difficulty" : 0.00001502,
"testnet" : false,
"keypoololdest" : 1441604161,
"keypoolsize" : 2,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
{
"version" : 301609,
"protocolversion" : 70009,
"walletversion" : 60000,
"balance" :
"darksend_balance" : 0.00000000,
"blocks" : 201385,
"timeoffset" : 0,
"moneysupply" : 19649228.99810293,
"connections" : 13,
"proxy" : "",
"difficulty" : 0.00001502,
"testnet" : false,
"keypoololdest" : 1441604161,
"keypoolsize" : 2,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
I see the difference in the number of my blocks and in block explorer: https://chainz.cryptoid.info/bcr/
201 385 and 200 740 respectively.
Probably block explorer: https://chainz.cryptoid.info/bcr/ and bittrex fall in one tree of the fork, since the funds on deposit bittrex not translated.
Synchronization was held from these peers: http://pastebin.com/hXtzY4mZ
Is there any other solution instead of waiting ? Because in the best scenario everybody are stuck at block 200740 and when you try to start a Banknode, your are 17 hours out of sync and it just will not start.
Sawa , can you check the time on your server? seems there is a 6 hour short fall somewhere and i can't find it on our side. Meanwhile, everyone who is upgrading, please YOU MUST RE-SYNC. Many peers are still broadcasting invalid blocks because they did not re-sync since we passed block 199999.
Please ensure you re-sync and are using 0.30.16.9 (or 0.30.17.0 for devs and testing) with 70009
I think we need to fast track the move to BN only mining because noone has managed to modify the p2pool code to handle the bidding process.
Please ensure you re-sync and are using 0.30.16.9 (or 0.30.17.0 for devs and testing) with 70009
I think we need to fast track the move to BN only mining because noone has managed to modify the p2pool code to handle the bidding process.
This fork, I stop p2pool
hack_, bitcreditscc ... witch is the correct chain ? .. there are multiple forks around
0.30.16.9-rc5 - Windows 64bit Wallet
Download Link: https://mega.nz/#!utsXSarK!9YXjdf5ls0cTyD1F99ZMcCLop-ZNvJf9c8IZisyUPUY
still crashing on "Done Loading". This is the report I get from windows:
Problem Event Name: APPCRASH
Application Name: bitcredit-qt.exe
Application Version: 0.3.16.9
Application Timestamp: a830a828
Fault Module Name: bitcredit-qt.exe
Fault Module Version: 0.3.16.9
Fault Module Timestamp: a830a828
Exception Code: c0000005
Exception Offset: 00000000009ed180
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 7891
Additional Information 2: 78919d816993304b4b9317e282839814
Additional Information 3: 4031
Additional Information 4: 4031ed150d0a4ca8f2c1b238e4acbfaf
Did you checked compability mode with Win 7 in bitcredit-qt.exe properities ?
Delete nodecache.dat, .lock , maybe another instance of exe is working in background.
One of my wallets only crash at close up, I think it's problem is localisation in default catalogue (c:\users\xxx\AppData\Roaming\ )
All the rest on desktop (with batch starting file bitcredit-qt.exe -datadir=C:\Users\xxx\Desktop\BCR-BN ...) works without problem.
With compatibility mode windows 7 it hangs on "loading wallet" all this even with an empty data folder.
0.30.16.9-rc5 - Windows 64bit Wallet
Download Link: https://mega.nz/#!utsXSarK!9YXjdf5ls0cTyD1F99ZMcCLop-ZNvJf9c8IZisyUPUY
still crashing on "Done Loading". This is the report I get from windows:
Problem Event Name: APPCRASH
Application Name: bitcredit-qt.exe
Application Version: 0.3.16.9
Application Timestamp: a830a828
Fault Module Name: bitcredit-qt.exe
Fault Module Version: 0.3.16.9
Fault Module Timestamp: a830a828
Exception Code: c0000005
Exception Offset: 00000000009ed180
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 7891
Additional Information 2: 78919d816993304b4b9317e282839814
Additional Information 3: 4031
Additional Information 4: 4031ed150d0a4ca8f2c1b238e4acbfaf
clean everything on %appdata%/Bitcredit except wallet.dat and bitcredit.conf and redownload the blockchain.
Tried that multiple times ..... still trying all sort of combinations.
0.30.16.9-rc5 - Windows 64bit Wallet
Download Link: https://mega.nz/#!utsXSarK!9YXjdf5ls0cTyD1F99ZMcCLop-ZNvJf9c8IZisyUPUY
still crashing on "Done Loading". This is the report I get from windows:
Problem Event Name: APPCRASH
Application Name: bitcredit-qt.exe
Application Version: 0.3.16.9
Application Timestamp: a830a828
Fault Module Name: bitcredit-qt.exe
Fault Module Version: 0.3.16.9
Fault Module Timestamp: a830a828
Exception Code: c0000005
Exception Offset: 00000000009ed180
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 7891
Additional Information 2: 78919d816993304b4b9317e282839814
Additional Information 3: 4031
Additional Information 4: 4031ed150d0a4ca8f2c1b238e4acbfaf
clean everything on %appdata%/Bitcredit except wallet.dat and bitcredit.conf and redownload the blockchain.
p2pool.website, bcrp2pool.website and sawa's pool are on fork ...
200829 on pools, 200734 on chainz https://chainz.cryptoid.info/bcr/
200829 on pools, 200734 on chainz https://chainz.cryptoid.info/bcr/
0.30.16.9-rc5 - Windows 64bit Wallet
Download Link: https://mega.nz/#!utsXSarK!9YXjdf5ls0cTyD1F99ZMcCLop-ZNvJf9c8IZisyUPUY
still crashing on "Done Loading". This is the report I get from windows:
Problem Event Name: APPCRASH
Application Name: bitcredit-qt.exe
Application Version: 0.3.16.9
Application Timestamp: a830a828
Fault Module Name: bitcredit-qt.exe
Fault Module Version: 0.3.16.9
Fault Module Timestamp: a830a828
Exception Code: c0000005
Exception Offset: 00000000009ed180
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 7891
Additional Information 2: 78919d816993304b4b9317e282839814
Additional Information 3: 4031
Additional Information 4: 4031ed150d0a4ca8f2c1b238e4acbfaf
Did you checked compability mode with Win 7 in bitcredit-qt.exe properities ?
Delete nodecache.dat, .lock , maybe another instance of exe is working in background.
One of my wallets only crash at close up, I think it's problem is localisation in default catalogue (c:\users\xxx\AppData\Roaming\ )
All the rest on desktop (with batch starting file bitcredit-qt.exe -datadir=C:\Users\xxx\Desktop\BCR-BN ...) works without problem.
Jump to: