here is a useful hint for people bidding and change addresses in a bitcoin client.
each time i send from my btc client, I dump the address i send from's privkey and import it into BCR with a label of bid date.
so the address i get paid to in BCR shows up under inputs as bid1115 for nov 15th.
since bitcoin uses change addresses any other coins in my bitcoin wallet from that input end up in a new address whose privkey i havent dumped or exposed
Since you are on github and have access, please open an issue there that i can track and come back to during coding. Already i've cleaned up the bidpage so adding additional stuff is not that hard. As for the other requests , let's list them as milestones on the git and we can pursue them.
Though...you do know that each new feature request == more code, more time, more delays , more study and more potential bugs.... so don't be too surprised if I push the rc further.
Let's just do what we can without too many delays. I'd like us to start the year with at least one working p2p service publicly released.
this is just an operations "best practice" suggestion, no code required.
looking for clarity on voting.
Adding:
ended up on a
fork an hour and 20 min ago, block height 251738,
chains shows block hash 001208333b6ca7e1ca9955825f3dac3ac5bebbdd210fe262e70f27a167f02a4b
wallet shows hash 0002ff305d9536c02cd593464331b08241bfaa7262693797bb83191674eea71b
instead of just getting stuck at invalid block like normal though my wallet is synced at block height
251795 hash 0002d8bd600d7e309ab3f0283973c6de4770b3b552f8210a4595035e0d065129
chainz 251795 hash 0003f7fc0224905770b7eff53169a5d5c75f5de43bb0ff95ebfaf92ffdf9bfd8
anyways this is a proper fork, it split 60 blocks ago and both sides are mining. and block height is within 1 block (im not currently mining nor have i been) Anyways I'm connected to 91.230.123.101:8888 version 0.30.17.8/, im the same version.
I will be deleting and re-syncing. I suggest whoever is 91.230.123.101:8888 do the same, and maybe someone upload a bootstrap from the same chain that the explorer is on.
while re-syncing I connect to 4 peers and instantly get booted down to this single peer. deleted peers.dat and removed 91.230.123.101 from conf file. im now stuck at 251737 with the chainz hash showing as invalid :/
2015-11-22 20:37:53 InvalidChainFound: invalid block=001208333b6ca7e1ca9955825f3dac3ac5bebbdd210fe262e70f27a167f02a4b height=251738 log2_work=35.94582 date=2015-11-22 19:04:34
tried sync again. stuck now for good
2015-11-22 20:52:58 UpdateTip: new best=0006eb215fe3f81487ee2671f1758f3be2a6896e25c0fd70e976d66d23154e75 height=251737 log2_work=35.94582 tx=260965 date=2015-11-22 19:04:15 progress=0.999303 cache=12
2015-11-22 20:52:58 ERROR: ConnectBlock(): banknode miningkey invalid
2015-11-22 20:52:58 InvalidChainFound: invalid block=001208333b6ca7e1ca9955825f3dac3ac5bebbdd210fe262e70f27a167f02a4b height=251738 log2_work=35.94582 date=2015-11-22 19:04:34
2015-11-22 20:52:58 InvalidChainFound: current best=0006eb215fe3f81487ee2671f1758f3be2a6896e25c0fd70e976d66d23154e75 height=251737 log2_work=35.94582 date=2015-11-22 19:04:15
2015-11-22 20:52:58 ERROR: ConnectTip(): ConnectBlock 001208333b6ca7e1ca9955825f3dac3ac5bebbdd210fe262e70f27a167f02a4b failed
2015-11-22 20:52:58 InvalidChainFound: invalid block=001208333b6ca7e1ca9955825f3dac3ac5bebbdd210fe262e70f27a167f02a4b height=251738 log2_work=35.94582 date=2015-11-22 19:04:34
2015-11-22 20:52:58 InvalidChainFound: current best=0006eb215fe3f81487ee2671f1758f3be2a6896e25c0fd70e976d66d23154e75 height=251737 log2_work=35.94582 date=2015-11-22 19:04:15
2015-11-22 20:52:58 ERROR: AcceptBlockHeader : block is marked invalid
2015-11-22 20:52:58 ERROR: invalid header received
maybe 251737 is the issue as it replies with mining key invalid but processes the block, and the next one becomes an invalid block and the fork starts there. it should have thrown out block 251737? or im reading it wrong. either way my client bans all its peers for giving it invalid blocks and connections goes to zero.