[ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 96.

rfcdejong

hero member

Activity: 798

Merit: 500

Quote from: rfcdejong on June 15, 2014, 10:56:17 AM

pool is jumping back in blocks anyway, from 16148 back to 16080

slimcoin 2014-6-15 15:54:29 UTC 16080 0000001fcbf2d2f5ff2e304d4517f38b69ac384623f78534bde921b5e8392174 15.04 immature
slimcoin 2014-6-15 15:49:19 UTC 16148 0000001558f86806b2ea117cc1085bcd4573307ffbf91df13bafd8e6007be65e 14.63 immature

and again from 16157 down to 16082

slimcoin 2014-6-15 17:34:44 UTC 16082 0000000485f1de64dd4d33d978c39ebf0f60fdb6b99c653aa3ef8981ba4bcbf9 14.97 immature
slimcoin 2014-6-15 17:31:45 UTC 16157 0000002419e0d82cefc25ae9d7e05ef7301af2223ceb2e80e800eccd649f1c16 15.96 immature

I would love to see the debug logs of that Wink

The dev will need it too

rfcdejong

hero member

Activity: 798

Merit: 500

pool is jumping back in blocks anyway, from 16148 back to 16080

slimcoin 2014-6-15 15:54:29 UTC 16080 0000001fcbf2d2f5ff2e304d4517f38b69ac384623f78534bde921b5e8392174 15.04 immature
slimcoin 2014-6-15 15:49:19 UTC 16148 0000001558f86806b2ea117cc1085bcd4573307ffbf91df13bafd8e6007be65e 14.63 immature

rfcdejong

hero member

Activity: 798

Merit: 500

Quote from: bitspender on June 15, 2014, 10:21:42 AM

Just post the pool's config file, so we can all sync on those nodes!!

After a relaunch if you ask me, it would be nice when the wallet is also fixed so they don't get stuck on PoS or PoB blocks...

bitspender

hero member

Activity: 658

Merit: 500

Just post the pool's config file, so we can all sync on those nodes!!

LIghtvelocityCoin

sr. member

Activity: 320

Merit: 250

totally give up.
Watch you guys play. Angry

rfcdejong

hero member

Activity: 798

Merit: 500

Quote from: primer- on June 15, 2014, 09:36:04 AM

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

That happens when you have blocks in your blockchain newer than the latest valid block from another 'fork', a corrupted blockchain..

The dev could perhaps add a condition to be able to skip that a hash of "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff"

rfcdejong

hero member

Activity: 798

Merit: 500

Quote from: slimcoin on June 15, 2014, 08:51:57 AM

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.

I wish i knew what the problem is, if it's PoS which causes issues then better remove PoS at all. Which open doors

Do you know which code is added / changed for dcrypt and PoB ? If so and if doable i suggest to take a fork from vertcoin, ignore the Script-N PoW and implement code for dcrypt and PoB. Remove the PoS which causes only trouble combined with PoB. All i know is that vertcoin has the best code vs litecoin by directly adding code from bitcoin.

And ofcourse offer a way to switch coins, best would be to let the new wallet work with the current blockchain, but that might be impossible because there is already PoS done. Maybe allow a service to exchange old coins to the new coins. Also burned coins should be able to be 'transfered' into the new coins.

primer-

legendary

Activity: 1092

Merit: 1000

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

Crljeni

member

Activity: 68

Merit: 10

Quote from: primer- on June 15, 2014, 09:14:06 AM

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.

What are we doing here? Trying daily to sync wallet !!!???

primer-

legendary

Activity: 1092

Merit: 1000

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.

jadefalke

legendary

Activity: 1456

Merit: 1014

fork @16k everything else sucks.

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: slimcoin on June 15, 2014, 08:51:57 AM

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

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: slimcoin on June 15, 2014, 08:51:57 AM

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 ?

slimcoin

full member

Activity: 182

Merit: 100

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.

Carey

member

Activity: 74

Merit: 10

Quote from: AizenSou on June 15, 2014, 08:26:51 AM

Quote from: bitspender on June 15, 2014, 08:24:54 AM

Quote from: bitspender on June 15, 2014, 08:13:16 AM

Looking to sell 1700 SLM, if anyone up for this, i sell at 0.0003

Nobody?

I don't think anyone will buy if we don't fix this mess.

i think this coin is too bad. Undecided

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: ShadowOfScales on June 15, 2014, 08:49:47 AM

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.

ShadowOfScales

full member

Activity: 138

Merit: 100

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.

rfcdejong

hero member

Activity: 798

Merit: 500

look what vericoin did to fix the sync problems

https://github.com/vericoin/master/commits/master/src/net.cpp

they added seed nodes

   {"dnsseed2", "dnsseed2.vericoin.info"},
   {"dnsseed3", "dnsseed3.vericoin.info"},
   {"dnsseed-pnosker", "dnsseed.pnosker.com"},
+ {"dnsseed-pcmerc", "dnsseed.kryptochaos.com"},
+ {"dnsseed-pcmerc2", "dnsseeds.kryptochaos.com"},
+ {"dnsseed-pcmerc3", "seed.kryptochaos.com"},

they turned off irc which was default on

https://github.com/vericoin/master/commit/811e7cda83a897c47623f4c4ef83f7e46a6b799e#diff-d8a18a64c865160e52a64a09ee6a289bL217

and added LOTS of checkpoints

But then still, the slimcoin wallet should first be fixed to not get stuck on PoS

mana6

sr. member

Activity: 354

Merit: 250

the burn time are too long,wish quickly,lol

primer-

legendary

Activity: 1092

Merit: 1000

Please shut down your wallets as well so we lower the difficulty

Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 96. (Read 284956 times)