Any working pool?
hack_ pools (my pools, but he runs them) are the most reliable, along with sawa's.
Topic: ◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈ - page 107. (Read 284526 times)
hack_ pools (my pools, but he runs them) are the most reliable, along with sawa's.
@hack_ : IPs of the pool nodes?
198.52.160.59
198.52.160.64
198.52.160.60
dev has another node, he'll be online today, finally got out hospital.
That is truly great news.
Thanks, time to get to work!!
So here is the gist of what i could glean,
1) There were multiple forks, i count 6
2) There was a group of solo miners who did not heed my decision to stick to the update and they now have 5K useless blocks.
3) Getblocktemplate was failing for some users because it assumes that the client is still downloading blocks if a certain amount of time has passed since th last block solved.
4) Some of the more stringent rules i placed in order to ensure network wide consensus on BNs were now preventing miners fro solving block 200000
5) Getwork was the quickest way around it using solo.
So since hack_ has the pools, i gave him the git password and some tips, seems he got most of it right, i'm just here to finish the job.
While i did have limited net access....i did have a laptop.... so expect some new code to go up for review, very very soon. (frustrated my friends to no end)
for direct contact please use [email protected], during the course of my detour , someone helped themselves to some of my belongings left in the flat including my phones.
@hack_ : IPs of the pool nodes?
198.52.160.59
198.52.160.64
198.52.160.60
dev has another node, he'll be online today, finally got out hospital.
Oy, it's a damn clinic!
@hack_ : IPs of the pool nodes?
198.52.160.59
198.52.160.64
198.52.160.60
dev has another node, he'll be online today, finally got out hospital.
That is truly great news.
@hack_ : IPs of the pool nodes?
198.52.160.59
198.52.160.64
198.52.160.60
dev has another node, he'll be online today, finally got out hospital.
Wow
Dev said clearly that we would move from the fork onwards. All blocks > 200008 have been mined with obsolete version. Check your wallet, if it does not have protocol version 70009 then it is on the wrong fork.
Many of you have not updated your wallet.
Dev said clearly that we would move from the fork onwards. All blocks > 200008 have been mined with obsolete version. Check your wallet, if it does not have protocol version 70009 then it is on the wrong fork.
Many of you have not updated your wallet.
So what's going on? I haven't opened this wallet for some time but it synched up for me. Block 206302 and showing 70 bank nodes.

{
"blocks" : 206302,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00000090,
"errors" : "",
"genproclimit" : -1,
"networkhashps" : 143,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : false,
"hashespermin" : 0
}

{
"blocks" : 206302,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00000090,
"errors" : "",
"genproclimit" : -1,
"networkhashps" : 143,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : false,
"hashespermin" : 0
}
At me it doesn't sync, it can't even get a connection somehow...
So what's going on? I haven't opened this wallet for some time but it synched up for me. Block 206302 and showing 70 bank nodes.

{
"blocks" : 206302,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00000090,
"errors" : "",
"genproclimit" : -1,
"networkhashps" : 143,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : false,
"hashespermin" : 0
}

{
"blocks" : 206302,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00000090,
"errors" : "",
"genproclimit" : -1,
"networkhashps" : 143,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : false,
"hashespermin" : 0
}
@hack_ : IPs of the pool nodes?
We are currently trying to solo block 200000, it's been two days
If anyone wants to help get the chain back online, download/build from the latest git commit and sync from the pool nodes i have set up. Then try mining the next block and we'll get to it. Dev relaxed some of the rules for a bit to ensure it's easier to get this done and will re-enforce them later.
If anyone wants to help get the chain back online, download/build from the latest git commit and sync from the pool nodes i have set up. Then try mining the next block and we'll get to it. Dev relaxed some of the rules for a bit to ensure it's easier to get this done and will re-enforce them later.
OK. I cant find the latest build. Give us the link.
Why for the previous wallet blockchain working good than?
How people mine BCR in that case, somebody constant mine ~ 20 BCR per block?
Give instruction how to mine solo?
We are currently trying to solo block 200000, it's been two days
If anyone wants to help get the chain back online, download/build from the latest git commit and sync from the pool nodes i have set up. Then try mining the next block and we'll get to it. Dev relaxed some of the rules for a bit to ensure it's easier to get this done and will re-enforce them later.
If anyone wants to help get the chain back online, download/build from the latest git commit and sync from the pool nodes i have set up. Then try mining the next block and we'll get to it. Dev relaxed some of the rules for a bit to ensure it's easier to get this done and will re-enforce them later.
I don't get it, the chain is moving on my end with the previous wallet, it says it's on block 205966
What am I supposed to do? update and get stuck at 19999 or stay on this one?
We are currently trying to solo block 200000, it's been two days
If anyone wants to help get the chain back online, download/build from the latest git commit and sync from the pool nodes i have set up. Then try mining the next block and we'll get to it. Dev relaxed some of the rules for a bit to ensure it's easier to get this done and will re-enforce them later.
If anyone wants to help get the chain back online, download/build from the latest git commit and sync from the pool nodes i have set up. Then try mining the next block and we'll get to it. Dev relaxed some of the rules for a bit to ensure it's easier to get this done and will re-enforce them later.
Somebody has some nodes that works with the last version? At first it was unstable between 0 and 1 node now it 0 at all.....
Any news?
Still waiting for a solution about the upgrade.
lg t.
Still waiting for a solution about the upgrade.
lg t.
Any working pool?
switched my nodes back to the previous wallet. Ready to update. Hopefully bitcreditscc is feeling better soon.
Any news ?
Resume:
1. Wallet 0.30.16.9-rc3 wont sync. Stuck on 199 999.
2. Wallet 0.30.16.8 sync. Nodes are mining no problem
3. Both of the pools are offline
1. Wallet 0.30.16.9-rc3 wont sync. Stuck on 199 999.
2. Wallet 0.30.16.8 sync. Nodes are mining no problem
3. Both of the pools are offline
Various fixes have been pushed to the repo, I'm just waiting for official word before updating all my BNs etc.
Resume:
1. Wallet 0.30.16.9-rc3 wont sync. Stuck on 199 999.
2. Wallet 0.30.16.8 sync. Nodes are mining no problem
3. Both of the pools are offline
1. Wallet 0.30.16.9-rc3 wont sync. Stuck on 199 999.
2. Wallet 0.30.16.8 sync. Nodes are mining no problem
3. Both of the pools are offline
I think that in this situation there are two options:
1. Make another fork. Then from 199999 block will turn on the new version of the protocol. And wallets of old and new versions will stop communicating.
2. Or cancel the upgrade and return to the older version of the core.
1. Make another fork. Then from 199999 block will turn on the new version of the protocol. And wallets of old and new versions will stop communicating.
2. Or cancel the upgrade and return to the older version of the core.
Hmmm, looking at things from my PoV, the pools are already upgraded according to hack_, the upgraded version works as expected..... i think we should force everyone to upgrade, as most of the stragglers are multiple BN owners who just do not want the hassle.
We had a similar situation where people tried to exploit the compatibility between upgrades , and i think we should forge ahead now like we did then.
I am going to release an minor update that cuts off old clients... If anyone disagrees, i'm open to discuss the issue for the next few hours, but after that we have to act decisively.
If you think everything will work, do it.
I am looking forward to placing my first BCR-backing bid.
Thanks for the support, my health is not yet back to 100% but i'll do what i can. It appears the exchange is stuck as well, we'll have to contact them.
Here's how we'll do it:-
The new version will be protocol 70009 on everything and will refuse to connect to older clients, meanwhile i will ask hack_ to upgrade again so that everyone can sync from the pools and avoid issues.
Last time when I checked, the p2pool was not working with the new wallet.
Please update de github and push the enforcing to, let's say 205000.
And we will see if the found it blocks are accepted by the new version.
As I understood it, there is no new version of the wallet. It has been announced only the number of communication protocol - 70009.
In order to p2pool work with this version of the protocol it is necessary to change in here:
https://github.com/bitcreditscc/p2pool/blob/master/p2pool/bitcoin/p2p.py#L21
these parameters
Code:
version=70008,
toCode:
version=70009,
To get rid of old shares it would be right to change these parameters too:https://github.com/bitcreditscc/p2pool/blob/master/p2pool/networks/bitcredit.py#L15
Code:
IDENTIFIER = 'b1dc7ed1dc11e0d1'.decode('hex')
PREFIX = 'ba0c05e7ad100301'.decode('hex')
And wait till bitcreditscc creates patch. PREFIX = 'ba0c05e7ad100301'.decode('hex')
Jump to: