|
Do we have an estimate for the relaunch ?
Dont worry about the blockchain, i've killed mine at block 16003, beyond me why some people kept it running.
|
|
|
|
|
When the time comes, I will host 10 or 20 supernodes, each one at a separate dedicated server. They should be able to handle/sync 5,000-10,000 clients.
|
|
|
|
We should pick a reference point closer to what the pool is at, then I will pause the pool while everyone can sync up. It's not true that only a select few people can mine, unless for solo mining. In fact most of the net hashrate is mining at the pool.
Sandor, dont be greedy, the block we agreed on is 16k. I've had my 150Kh/s pointed at the pool all day today but its just not fair to the others. Kill the pool. Relaunch at 16k Hey I'm not being greedy, but what about the other 52 people mining at the pool? That guy with 1Mh will be crying. I've been yelling stop sending hash to the pool since block 15900. F... him. Only the greedy are expecting the payment. I am not and my hash was at the pool. |
|
|
|
We should pick a reference point closer to what the pool is at, then I will pause the pool while everyone can sync up. It's not true that only a select few people can mine, unless for solo mining. In fact most of the net hashrate is mining at the pool.
Sandor, dont be greedy, the block we agreed on is 16k. I've had my 150Kh/s pointed at the pool all day today but its just not fair to the others. Kill the pool. Relaunch at 16k |
|
|
|
|
Heres another bug that cripples the database
ERROR: HashBurnData() : Burn transaction does not meet minimum number of confirmations 0 < 6
ERROR: CheckProofOfBurnHash() : hash doesn't match nBurnBits
ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff > 000000023e1c0000000000000000000000000000000000000000000000000000
ERROR: bool CTxDB::LoadBlockIndex() : deserialize error on PoB index 16034
Error loading blkindex.dat
|
|
|
|
when the coin launch? I care about this.
Almost certainly before 13 June. I will announce within a week. SunnyPrince has been arrested for pedofilia on 12. June - a 13 year old boy was rescued from his trailer camp in Madison. |
|
|
|
WTS 2,000,000 Shinycoins  |
|
|
|
|
This shit coin needs to go back into development stage and re-launch at block 16k in a couple of weeks when all bugs are patched.
I'm out.
EDIT: Sandor shut your pool down, and your nodes. We need to kill the coin to get some attention from the dev.
EDIT2: Dev does not know what he is doing. This coin is dead unless someone else takes over.
|
|
|
|
I do not think the issue is in the PoS blocks. As for the stop at block 16000, I will have to create a hard fork from there, that is if I see more people wanting such fork.
Pool is getting all the blocks (with 1/10 of the total network hash power) and there are only 5 or so miners sending hash power to the pool. If you dont fork at 16000 we are all fools. http://slimcoinpool.com/tbs |
|
|
|
Anyone that has had syncing issues and has investigated it, please give me your *detailed* input please.
What I have noticed is that:
PoB blocks have DoS protection that bans good nodes if too many orphan PoB blocks are sent.
PoB blocks cannot be orphaned (yet), if an orphaned PoB block is sent, it will get rejected and not recorded anywhere.
I put such DoS protection to prevent any malicious activity, but it seems it is doing more harm that good.
I do not think the issue is in the PoS blocks. As for the stop at block 16000, I will have to create a hard fork from there, that is if I see more people wanting such fork.
The intermediate burn hash fix that takes affect at block 17000 fixes: A PoB block can be falsely rejected due to inaccuracy in floating point precision between two different machines. Some nodes will accept it and others will not (and this will not be able to get to the other blocks after it). This intermediate burn hash fix, does fix this, it is not a patch.
Are you saying wallet will have no issues syncing from block 17000 ? |
|
|
|
primer-, out of curiousity.
You seem to have been attacking the coin previously, yet boasting of a hash-rate above what most of us have.
Is this goading to stop mining yet another means for you to profit?
I'm waiting for official notice from the dev before I take you seriously.
There's been instructions on this forum for a while now, allowing anyone who bothers to read, to sync correctly.
Are you going to use that high amount of khash to solo, after you successfully fool people into stopping mining?
I believe this is the case, and there's no evidence to disprove me currently.
Read the last 10 pages idiot. The instructions to sync were provided by me. Good luck syncing now that i shut off my nodes. |
|
|
|
|
Please shut down your wallets as well so we lower the difficulty
|
|
|
|
Please stop sending the pool your hash power, this instamine has to stop. Dev. will use block 16000 as the beginning block after the fork.
Can't stop this. I have more than 80 servers sending my hash to the pool. I've paid for them, so i'll use them. Are you going to compensate whatever hours loss i have for not mining?  You will not get any SLM after the fork my friend. Everything above block 16000 will be discarded. Pool is instamining. Did the dev accept block 16000 ? I didn't see an announcement from him. No but any other decision would be unfair. There is now over 6MH/s in the 'network' but pool is getting 99% of the blocks with only 1.8MH/s. Instamine... |
|
|
|
Please stop sending the pool your hash power, this instamine has to stop. Dev. will use block 16000 as the beginning block after the fork.
Can't stop this. I have more than 80 servers sending my hash to the pool. I've paid for them, so i'll use them. Are you going to compensate whatever hours loss i have for not mining? You will not get any SLM after the fork my friend. Everything above block 16000 will be discarded. Pool is instamining. |
|
|
|
|
Please stop sending the pool your hash power, this instamine has to stop. Dev. will use block 16000 as the beginning block after the fork.
|
|
|
|
|
My nodes are now down. Blockchain archived.
|
|
|
|
I will be shutting off my nodes at block 16000. I'll archive it and keep it for the dev if he requests a copy. I would like to see sandor do the same, what we have now is just nonsense.
Time for a shutdown and rebuild. What you have now is just another disaster in the making. Power it down, hard fork it, then sync it back up. (After testing it properly.) +1 |
|
|
|
it seems the fix of the dev kicks in at block 17000 ?
+#define BURN_INTERMEDIATE_HEIGHT 17000
the question is what that really does, intermediate burn fix.
Probably NOTHING... |
|
|
|
|
I will be shutting off my nodes at block 16000. I'll archive it and keep it for the dev if he requests a copy. I would like to see sandor do the same, what we have now is just nonsense.
|
|
|
|
I'm at 15978
You are there now but you will go out of sync sooner or later. |
|
|
|
|
Show Posts
