dont get the brains lol
Topic: [ANN][SEED] SeedCoin | New Road Map - page 68. (Read 184103 times)
new block explorer please
dont get the brains lol
dont get the brains lol
ok i am staking now on wallet 1.0.5 and have to go to bed so i hope everything works well from now
i got
23:50:18

{
"hash" : "3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0",
"confirmations" : 14,
"size" : 444,
"height" : 11321,
"version" : 1,
"merkleroot" : "1a20da2d0b4442d2ee718372d7c1bc68e0ea19c97cbb8de7f39fbc690ef68ab2",
"mint" : 0.14349248,
"time" : 1413059943,
"nonce" : 0,
"bits" : "1e69c5b7",
"difficulty" : 0.00003693,
"blocktrust" : "26b98",
"chaintrust" : "28e49fc4df51da",
"previousblockhash" : "62364289c04cd185ae529caf9139c2f9c3d367c428ab8d537bbc5ce4b864a7b8",
"nextblockhash" : "24a4bbdacdfc518ca5396f601daa2a532c712f5bd6c5b16125388f0c937dd9d7",
"flags" : "proof-of-stake",
"proofhash" : "0003fa27fbe95d5fa800633cdb14f6b4a704f17c7d51836065b7ae565b5f5822",
"entropybit" : 0,
"modifier" : "406f00d126e815e9",
"modifierchecksum" : "c85938aa",
"tx" : [
"19b8ccba2ab3ac4a1a5dad61e4cb179c8d86b4dfbff00ac2e38c80bf6f41c62a",
"88d91dfde6471fcd7a45a2aa52e933ac6a5b04acaa1057f4e3f57c0db40a70f1"
],
"signature" : "3045022100af068f1171b3b85355d5cd2c967e156efc46d5fe68cecbf8ae284da82ee7ff8502202 c93db2224b563a7ce84a627d20b67bb9227b0cb1128bd0bf8fe562c4cebfd27"
}
23:50:18

{
"hash" : "3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0",
"confirmations" : 14,
"size" : 444,
"height" : 11321,
"version" : 1,
"merkleroot" : "1a20da2d0b4442d2ee718372d7c1bc68e0ea19c97cbb8de7f39fbc690ef68ab2",
"mint" : 0.14349248,
"time" : 1413059943,
"nonce" : 0,
"bits" : "1e69c5b7",
"difficulty" : 0.00003693,
"blocktrust" : "26b98",
"chaintrust" : "28e49fc4df51da",
"previousblockhash" : "62364289c04cd185ae529caf9139c2f9c3d367c428ab8d537bbc5ce4b864a7b8",
"nextblockhash" : "24a4bbdacdfc518ca5396f601daa2a532c712f5bd6c5b16125388f0c937dd9d7",
"flags" : "proof-of-stake",
"proofhash" : "0003fa27fbe95d5fa800633cdb14f6b4a704f17c7d51836065b7ae565b5f5822",
"entropybit" : 0,
"modifier" : "406f00d126e815e9",
"modifierchecksum" : "c85938aa",
"tx" : [
"19b8ccba2ab3ac4a1a5dad61e4cb179c8d86b4dfbff00ac2e38c80bf6f41c62a",
"88d91dfde6471fcd7a45a2aa52e933ac6a5b04acaa1057f4e3f57c0db40a70f1"
],
"signature" : "3045022100af068f1171b3b85355d5cd2c967e156efc46d5fe68cecbf8ae284da82ee7ff8502202 c93db2224b563a7ce84a627d20b67bb9227b0cb1128bd0bf8fe562c4cebfd27"
}
@Wiser: yes, for block 11321, I had correct response too, you can check the block 11329 from my previous post if it is same.
I know it sucks and I know I said go to 1.0.4, but bittrex is going to 1.0.5 so everyone needs to go to 1.0.5 and resync immediately.
The block explorer is forked from 1.0.4 and is not on the right block. Nodes are resyncing. The proper hash for block 11321 is 3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0
Go to help > debug window and type getblock 3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0
If you get an error you need to get 1.0.5 and delete the stuff in %appdata%/seedcoin except for your wallet.dat file
This will not happen again. I'm not touching the staking algo again, or anything else that effects the network, and any core updates will be thoroughly tested over the course of several weeks before release, and there will be months of lead time to get the correct version.
The block explorer is forked from 1.0.4 and is not on the right block. Nodes are resyncing. The proper hash for block 11321 is 3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0
Go to help > debug window and type getblock 3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0
If you get an error you need to get 1.0.5 and delete the stuff in %appdata%/seedcoin except for your wallet.dat file
This will not happen again. I'm not touching the staking algo again, or anything else that effects the network, and any core updates will be thoroughly tested over the course of several weeks before release, and there will be months of lead time to get the correct version.
1 exception. I'll be setting checkpoints after the growth period ends that will allow wallets to more easily navigate the mess of a blockchain we have right now. That will solve most of the syncing issues. But again, even that will be thoroughly tested and run for along period of time and I will be absolutely 100% sure that it is compatable with the current network. It will be an optional update. Period.
I got this:
{
"hash" : "3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0",
"confirmations" : 9,
"size" : 444,
"height" : 11321,
"version" : 1,
"merkleroot" : "1a20da2d0b4442d2ee718372d7c1bc68e0ea19c97cbb8de7f39fbc690ef68ab2",
"mint" : 0.14349248,
"time" : 1413059943,
"nonce" : 0,
"bits" : "1e69c5b7",
"difficulty" : 0.00003693,
"blocktrust" : "26b98",
"chaintrust" : "28e49fc4df51da",
"previousblockhash" : "62364289c04cd185ae529caf9139c2f9c3d367c428ab8d537bbc5ce4b864a7b8",
"nextblockhash" : "24a4bbdacdfc518ca5396f601daa2a532c712f5bd6c5b16125388f0c937dd9d7",
"flags" : "proof-of-stake",
"proofhash" : "0003fa27fbe95d5fa800633cdb14f6b4a704f17c7d51836065b7ae565b5f5822",
"entropybit" : 0,
"modifier" : "406f00d126e815e9",
"modifierchecksum" : "c85938aa",
"tx" : [
"19b8ccba2ab3ac4a1a5dad61e4cb179c8d86b4dfbff00ac2e38c80bf6f41c62a",
"88d91dfde6471fcd7a45a2aa52e933ac6a5b04acaa1057f4e3f57c0db40a70f1"
],
"signature" : "3045022100af068f1171b3b85355d5cd2c967e156efc46d5fe68cecbf8ae284da82ee7ff8502202 c93db2224b563a7ce84a627d20b67bb9227b0cb1128bd0bf8fe562c4cebfd27"
}
Is that good?
{
"hash" : "3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0",
"confirmations" : 9,
"size" : 444,
"height" : 11321,
"version" : 1,
"merkleroot" : "1a20da2d0b4442d2ee718372d7c1bc68e0ea19c97cbb8de7f39fbc690ef68ab2",
"mint" : 0.14349248,
"time" : 1413059943,
"nonce" : 0,
"bits" : "1e69c5b7",
"difficulty" : 0.00003693,
"blocktrust" : "26b98",
"chaintrust" : "28e49fc4df51da",
"previousblockhash" : "62364289c04cd185ae529caf9139c2f9c3d367c428ab8d537bbc5ce4b864a7b8",
"nextblockhash" : "24a4bbdacdfc518ca5396f601daa2a532c712f5bd6c5b16125388f0c937dd9d7",
"flags" : "proof-of-stake",
"proofhash" : "0003fa27fbe95d5fa800633cdb14f6b4a704f17c7d51836065b7ae565b5f5822",
"entropybit" : 0,
"modifier" : "406f00d126e815e9",
"modifierchecksum" : "c85938aa",
"tx" : [
"19b8ccba2ab3ac4a1a5dad61e4cb179c8d86b4dfbff00ac2e38c80bf6f41c62a",
"88d91dfde6471fcd7a45a2aa52e933ac6a5b04acaa1057f4e3f57c0db40a70f1"
],
"signature" : "3045022100af068f1171b3b85355d5cd2c967e156efc46d5fe68cecbf8ae284da82ee7ff8502202 c93db2224b563a7ce84a627d20b67bb9227b0cb1128bd0bf8fe562c4cebfd27"
}
Is that good?
I know it sucks and I know I said go to 1.0.4, but bittrex is going to 1.0.5 so everyone needs to go to 1.0.5 and resync immediately.
The block explorer is forked from 1.0.4 and is not on the right block. Nodes are resyncing. The proper hash for block 11321 is 3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0
Go to help > debug window and type getblock 3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0
If you get an error you need to get 1.0.5 and delete the stuff in %appdata%/seedcoin except for your wallet.dat file
This will not happen again. I'm not touching the staking algo again, or anything else that effects the network, and any core updates will be thoroughly tested over the course of several weeks before release, and there will be months of lead time to get the correct version.
The block explorer is forked from 1.0.4 and is not on the right block. Nodes are resyncing. The proper hash for block 11321 is 3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0
Go to help > debug window and type getblock 3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0
If you get an error you need to get 1.0.5 and delete the stuff in %appdata%/seedcoin except for your wallet.dat file
This will not happen again. I'm not touching the staking algo again, or anything else that effects the network, and any core updates will be thoroughly tested over the course of several weeks before release, and there will be months of lead time to get the correct version.
I know it sucks and I know I said go to 1.0.4, but bittrex is going to 1.0.5 so everyone needs to go to 1.0.5 and resync immediately.
The block explorer is forked from 1.0.4 and is not on the right block. Nodes are resyncing. The proper hash for block 11321 is 3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0
Go to help > debug window and type getblock 3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0
If you get an error you need to get 1.0.5 and delete the stuff in %appdata%/seedcoin except for your wallet.dat file
This will not happen again. I'm not touching the staking algo again, or anything else that effects the network, and any core updates will be thoroughly tested over the course of several weeks before release, and there will be months of lead time to get the correct version.
The block explorer is forked from 1.0.4 and is not on the right block. Nodes are resyncing. The proper hash for block 11321 is 3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0
Go to help > debug window and type getblock 3d67968e7539234c9c8402b6d4a48022e63277e57b424fa6d3b89eb28e6eacd0
If you get an error you need to get 1.0.5 and delete the stuff in %appdata%/seedcoin except for your wallet.dat file
This will not happen again. I'm not touching the staking algo again, or anything else that effects the network, and any core updates will be thoroughly tested over the course of several weeks before release, and there will be months of lead time to get the correct version.
Alright. Here's the situation. People are staking into a new fork with the new wallets. The new wallets fork into this chain. I know it's a shitshow guys, but I think our only choice is to roll with it and get everyone updated to 1.0.5 asap. Once everyone's updated, then the 1.0.5's can stake.
I don't honestly know why 1.0.4's aren't accepting 1.0.5 blocks. But they're not. With 'trex updating to 1.0.5 now, there's just no choice. We have to go with it. I know I've been knee-jerking into trying to fix everything, but the fact is 1.0.5 has gone off on it's own fork, and we either all need to join up on it, or that's pretty much it.
Last update I`ve seen.
[Edit]
We will need some check information, if we are on correct chain,
getblockhash 11329 gets me 3ccebfe90047e764fa80cb4ecf69bade3a68f3e19eb0f1f6285981ea340d0cc4
Little confused dev's said go back to version 4 or lock version 5 wallet. Is that not correct?
Oh man, just finished my downgrades to 1.0.4
So back to 1.0.5.
Hope this is the final change, as bittrex doing 1.0.5 and I`m going to bed soon.
So back to 1.0.5.
Hope this is the final change, as bittrex doing 1.0.5 and I`m going to bed soon.
Since others are staking with version 5, then I'm unlocking. It seems the latest is that we all have to go along with v. 5 because that's what BitTrex is on.
Cryptzo, if staking with v. 5 is bad, though, please say so. It's hard to know what's best right now. I'm sure you're working on it.
Cryptzo, if staking with v. 5 is bad, though, please say so. It's hard to know what's best right now. I'm sure you're working on it.
Wiser, nice post count!
Since others are staking with version 5, then I'm unlocking. It seems the latest is that we all have to go along with v. 5 because that's what BitTrex is on.
Cryptzo, if staking with v. 5 is bad, though, please say so. It's hard to know what's best right now. I'm sure you're working on it.
Cryptzo, if staking with v. 5 is bad, though, please say so. It's hard to know what's best right now. I'm sure you're working on it.
My complaint is simple - the ongoing problems with staking and freezing of the coin on trex has permanently hurt the value of this coin - It was off to a great start and then things went downhill and continue downhill.
This is not what I bought into - we were sold a myth, not a coin even before mining began the devs were back pedaling on promises made in the ICO - therefore the ICO was not legitimate.
Syscoin had problem similar and it has never recovered and to this still is still in the tank.
This is not what I bought into - we were sold a myth, not a coin even before mining began the devs were back pedaling on promises made in the ICO - therefore the ICO was not legitimate.
Syscoin had problem similar and it has never recovered and to this still is still in the tank.
The ICO was never legitimate since no one told no ones that this was simply a rushed hackjob/copy/paste of Shadowcoin.... with the 269% gimmick. That was DISCOVERED (and subsequently admitted by the dev, of course) by one investor. Even before the discovery, I had been posting already that there was no innovation whatsoever on this project, just a gimmick designed to first attract ICO money -a total miserable failure- and second, to cater to the blind, greedy idiots.
Besides these two clearly stated points, the dev himself had clearly stated that he expected to be handsomely compensated, and in advance, through the ICO, for his future involvement in the coin, because he doesn't "... believe in voluntary dev work."
Now, no matter how you choose to cocktail-ize these ingredients, you are going to end up with less or no money and a mess.
But yes, sorry, this is what you chose to buy into.
yo we are trying something new, as stated earlier this is an experiment
since 11:57 MST I have been mining -SEED see transaction from 11:57. Every transaction after has been negative
Status: 106 confirmations
Date: 10/11/2014 11:57
Source: Generated
Debit: 0.00 SEED
Net amount: -0.07849279 SEED
Transaction ID: 6b91a8c08cc6adce74b8ae7558e30691e848d647ab3ca0cbdcd0ff58d136e81f
Generated coins must mature 120 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.
Status: 106 confirmations
Date: 10/11/2014 11:57
Source: Generated
Debit: 0.00 SEED
Net amount: -0.07849279 SEED
Transaction ID: 6b91a8c08cc6adce74b8ae7558e30691e848d647ab3ca0cbdcd0ff58d136e81f
Generated coins must mature 120 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.
it shows negative until if fully confirms.
I seem to be staking just fine with 1.0.5 ... with one of the larger wallets
Have you actually gotten a reward? Or is it just showing you that it is staking?
check which block you are on my 1.0.5.0 was ahead. Mine was ahead of the seedcoin block explorer. I deleted all files except wallet.dat and peers.dat and fired up 1.0.4.0 and now I am on the correct block.
I am staking with 1.0.5 now
since 11:57 MST I have been mining -SEED see transaction from 11:57. Every transaction after has been negative
Status: 106 confirmations
Date: 10/11/2014 11:57
Source: Generated
Debit: 0.00 SEED
Net amount: -0.07849279 SEED
Transaction ID: 6b91a8c08cc6adce74b8ae7558e30691e848d647ab3ca0cbdcd0ff58d136e81f
Generated coins must mature 120 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.
Status: 106 confirmations
Date: 10/11/2014 11:57
Source: Generated
Debit: 0.00 SEED
Net amount: -0.07849279 SEED
Transaction ID: 6b91a8c08cc6adce74b8ae7558e30691e848d647ab3ca0cbdcd0ff58d136e81f
Generated coins must mature 120 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.
Wiser- reward
Great! Cryptzo, can I stake wtih my v. 5 now?
I'm getting a bit confused with some of the conflicting messages--from you
So please give me the latest. To stake or not to stake, that is the question.EDIT: I briefly unlocked my version 5 and I'm due to stake in 12 minutes. Then I locked it again. So... can you please answer my question quickly? Thanks.
Wiser- reward
Jump to: