Obsidian ODN - CryptoCurrency & Secure Anonymous Messaging - page 49.

Darkoth89

hero member

Activity: 1274

Merit: 646

Quote from: Mt_Traditional on September 02, 2017, 10:37:22 AM

Hi OBSIDIAN, When will investors be able to withdraw their tokens?
Pls give us a distribution date for the tokens.

Shocked

I think they are testing the wallet and ensuring it's working fine before sending out the ICO tokens!

Mt_Traditional

member

Activity: 72

Merit: 10

Hi OBSIDIAN, When will investors be able to withdraw their tokens?
Pls give us a distribution date for the tokens.

Shocked

jukKas

full member

Activity: 364

Merit: 100

How I have missed this project and ICO. Seems very promising and teams giving professional appearance.

Will be watching and definitely grabbing some OND's when this starts hitting legit exchanges.

Good luck!

luxulus

newbie

Activity: 12

Merit: 0

Quote from: onedeveloper on September 02, 2017, 05:32:15 AM

All this kind of problems are due to the fact that there're so many miners creating blocks at fast speed. Some of the blocks get "out-of-sync" with the network (the "too early" errors) and others just are superseded by a previously mined block on the blockchain, and to avoid creating a fork, they are automatically discarded (the "REORGANIZE" messages).

When the network is fully PoS those messages will start dissapearing due to the different algorithm managing the staking. Ah .. and some of the mined blocks are rejected due to a "proof-of-stake" block found first and these take precedence.

I hope this explaination is not too technical and you can understand it Cool

That's fine thanks Wink

After all I managed to get the wallet running on Ubuntu 17.04, my knowledge is constantly rising as we speak Grin

Another question though: I'd like to know more about master nodes, can you please direct me to some discussion/documentation?

onedeveloper

full member

Activity: 143

Merit: 100

Quote from: luxulus on September 02, 2017, 05:18:11 AM

Quote from: luxulus on September 02, 2017, 04:50:23 AM

Don't know why, only know it happened me 8 times and only 1 block was credited to my wallet.

After more analysis, it turns out that, out of these 8 times a new block was found, "ERROR: AcceptBlock()" was triggered 6 times, while in the other instances I got:

Code:

CheckWork() : new proof-of-work block found
proof hash: 00000000486a2ca96a044c9bbe628c1a334356ef49f7ad3af63890558a9fa1d0
target: 000000005818c600000000000000000000000000000000000000000000000000
CBlock(hash=0af4830d9ce404d5b7fe163c7afc8314b96abc2915766bea222a59db5199c55b, ver=7, hashPrevBlock=f34845a0dafa1161726930992e0d0a20c8a530ecad401c4984ddb32c62315d28, hashMerkleRoot=0808bdd904183c6cf810f7cfd3f8$
Coinbase(hash=0808bdd904183c6cf810f7cfd3f8dddd7796387f220383859a7affe0f91d0503, nTime=1504310401, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, 4294967295), coinbase 028e2b0101)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 a37e0d6ccc7e3ed254d1d990f8f8d6af7053d710 OP_EQUALVERIFY OP_CHECKSIG)

vMerkleTree: 0808bdd904183c6cf810f7cfd3f8dddd7796387f220383859a7affe0f91d0503

generated 4.00
keypool keep 7
AddToWallet 0808bdd904183c6cf810f7cfd3f8dddd7796387f220383859a7affe0f91d0503 new
SetBestChain: new best=0af4830d9ce404d5b7fe163c7afc8314b96abc2915766bea222a59db5199c55b height=11150 trust=145514044351268806619 blocktrust=12480725596 date=09/02/17 00:00:16
ProcessBlock: ACCEPTED
keypool added key 108, size=101
keypool reserve 8
REORGANIZE
REORGANIZE: Disconnect 1 blocks; f34845a0dafa1161726930992e0d0a20c8a530ecad401c4984ddb32c62315d28..0af4830d9ce404d5b7fe163c7afc8314b96abc2915766bea222a59db5199c55b
REORGANIZE: Connect 1 blocks; f34845a0dafa1161726930992e0d0a20c8a530ecad401c4984ddb32c62315d28..de2429afaae3b1dc991ad4112e06335ef6364dfd2dca6e677430c30930544195
REORGANIZE: done

which was NOT credited, and

Code:

CheckWork() : new proof-of-work block found
proof hash: 0000000046b9fa8caf298642389086beaef341b9ca4f79cba8b5493894d530cf
target: 0000000097f40000000000000000000000000000000000000000000000000000
CBlock(hash=086fd38cc5d43d1bb2be800cfa402476498b4e41a9c0e2c68f9f53f8ee0ed2d3, ver=7, hashPrevBlock=03c268ecd778c622d4a631ae76e59e626825e0ded1024b8bef8c963bc40642ae, hashMerkleRoot=5036ff09695329beebff3d608e73$
Coinbase(hash=5036ff09695329beebff3d608e73ae96abf7d69cc1176b7320a4cb48ff039a11, nTime=1504333570, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, 4294967295), coinbase 02212e0101)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 3e742215294dc924c7c85575d291f6b66e617b1a OP_EQUALVERIFY OP_CHECKSIG)

vMerkleTree: 5036ff09695329beebff3d608e73ae96abf7d69cc1176b7320a4cb48ff039a11

generated 4.00
keypool keep 9
AddToWallet 5036ff09695329beebff3d608e73ae96abf7d69cc1176b7320a4cb48ff039a11 new
SetBestChain: new best=086fd38cc5d43d1bb2be800cfa402476498b4e41a9c0e2c68f9f53f8ee0ed2d3 height=11809 trust=158765568409155339721 blocktrust=7235860583 date=09/02/17 06:26:16
ProcessBlock: ACCEPTED
keypool added key 110, size=101
keypool reserve 10

which was instead credited.

All this kind of problems are due to the fact that there're so many miners creating blocks at fast speed. Some of the blocks get "out-of-sync" with the network (the "too early" errors) and others just are superseded by a previously mined block on the blockchain, and to avoid creating a fork, they are automatically discarded (the "REORGANIZE" messages).

When the network is fully PoS those messages will start dissapearing due to the different algorithm managing the staking. Ah .. and some of the mined blocks are rejected due to a "proof-of-stake" block found first and these take precedence.

I hope this explaination is not too technical and you can understand it Cool

luxulus

newbie

Activity: 12

Merit: 0

Quote from: luxulus on September 02, 2017, 04:50:23 AM

Don't know why, only know it happened me 8 times and only 1 block was credited to my wallet.

After more analysis, it turns out that, out of these 8 times a new block was found, "ERROR: AcceptBlock()" was triggered 6 times, while in the other instances I got:

Code:

CheckWork() : new proof-of-work block found
proof hash: 00000000486a2ca96a044c9bbe628c1a334356ef49f7ad3af63890558a9fa1d0
target: 000000005818c600000000000000000000000000000000000000000000000000
CBlock(hash=0af4830d9ce404d5b7fe163c7afc8314b96abc2915766bea222a59db5199c55b, ver=7, hashPrevBlock=f34845a0dafa1161726930992e0d0a20c8a530ecad401c4984ddb32c62315d28, hashMerkleRoot=0808bdd904183c6cf810f7cfd3f8$
Coinbase(hash=0808bdd904183c6cf810f7cfd3f8dddd7796387f220383859a7affe0f91d0503, nTime=1504310401, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, 4294967295), coinbase 028e2b0101)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 a37e0d6ccc7e3ed254d1d990f8f8d6af7053d710 OP_EQUALVERIFY OP_CHECKSIG)

vMerkleTree: 0808bdd904183c6cf810f7cfd3f8dddd7796387f220383859a7affe0f91d0503

generated 4.00
keypool keep 7
AddToWallet 0808bdd904183c6cf810f7cfd3f8dddd7796387f220383859a7affe0f91d0503 new
SetBestChain: new best=0af4830d9ce404d5b7fe163c7afc8314b96abc2915766bea222a59db5199c55b height=11150 trust=145514044351268806619 blocktrust=12480725596 date=09/02/17 00:00:16
ProcessBlock: ACCEPTED
keypool added key 108, size=101
keypool reserve 8
REORGANIZE
REORGANIZE: Disconnect 1 blocks; f34845a0dafa1161726930992e0d0a20c8a530ecad401c4984ddb32c62315d28..0af4830d9ce404d5b7fe163c7afc8314b96abc2915766bea222a59db5199c55b
REORGANIZE: Connect 1 blocks; f34845a0dafa1161726930992e0d0a20c8a530ecad401c4984ddb32c62315d28..de2429afaae3b1dc991ad4112e06335ef6364dfd2dca6e677430c30930544195
REORGANIZE: done

which was NOT credited, and

Code:

CheckWork() : new proof-of-work block found
proof hash: 0000000046b9fa8caf298642389086beaef341b9ca4f79cba8b5493894d530cf
target: 0000000097f40000000000000000000000000000000000000000000000000000
CBlock(hash=086fd38cc5d43d1bb2be800cfa402476498b4e41a9c0e2c68f9f53f8ee0ed2d3, ver=7, hashPrevBlock=03c268ecd778c622d4a631ae76e59e626825e0ded1024b8bef8c963bc40642ae, hashMerkleRoot=5036ff09695329beebff3d608e73$
Coinbase(hash=5036ff09695329beebff3d608e73ae96abf7d69cc1176b7320a4cb48ff039a11, nTime=1504333570, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, 4294967295), coinbase 02212e0101)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 3e742215294dc924c7c85575d291f6b66e617b1a OP_EQUALVERIFY OP_CHECKSIG)

vMerkleTree: 5036ff09695329beebff3d608e73ae96abf7d69cc1176b7320a4cb48ff039a11

generated 4.00
keypool keep 9
AddToWallet 5036ff09695329beebff3d608e73ae96abf7d69cc1176b7320a4cb48ff039a11 new
SetBestChain: new best=086fd38cc5d43d1bb2be800cfa402476498b4e41a9c0e2c68f9f53f8ee0ed2d3 height=11809 trust=158765568409155339721 blocktrust=7235860583 date=09/02/17 06:26:16
ProcessBlock: ACCEPTED
keypool added key 110, size=101
keypool reserve 10

which was instead credited.

luxulus

newbie

Activity: 12

Merit: 0

Quote from: kurret on September 02, 2017, 03:38:08 AM

What does this mean? My guess is that my computer managed to find a new block, but it then failed to broadcast it to the network (I did not manage to mine any coins so far). Anyone knows why it fails?

you can find the debug log under Debug window->Information->Debug log file: open

Don't know why, only know it happened me 8 times and only 1 block was credited to my wallet.

kurret

member

Activity: 91

Merit: 10

I have a question about the debug log, mostly just out of curiosity. Most lines say something like

Code:

SetBestChain: new best=f91686f21640f4a6abe67a5ac14de2ef5888224113ccade770f5700ae9df959b height=9224 trust=121434266866692311117 blocktrust=7542808283 date=09/01/17 05:09:42
ProcessBlock: ACCEPTED

which I guess means that someone else found a block and it was accepted by my client. However, sometimes it would say something like

Code:

CheckWork() : new proof-of-work block found
proof hash: 000000009351076610afa150c98ce038d182eb14080be82faf96d7985c278521
target: 00000000c7df0000000000000000000000000000000000000000000000000000
CBlock(hash=28121b930d3d5bf17e2b191ddad3590117ed68fcaf02b232cdebdbe87b5d964a, ver=7, hashPrevBlock=0337d7a6d73439fd51bcf74ce6a5a5b7a2b245e8808b83191189b58976249641, hashMerkleRoot=963557a0bb52d30ed7941d3434ea7a324bd6e56fb83f6b489ee9554a989155f4, nTime=1504294526, nBits=1d00c7df, nNonce=110132736, vtx=1, vchBlockSig=)
Coinbase(hash=963557a0bb52d30ed7941d3434ea7a324bd6e56fb83f6b489ee9554a989155f4, nTime=1504294450, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, 4294967295), coinbase 02d1290101)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 a173a193859b15c679bc6aa5e4b3d53a6ad4fe8f OP_EQUALVERIFY OP_CHECKSIG)

vMerkleTree: 963557a0bb52d30ed7941d3434ea7a324bd6e56fb83f6b489ee9554a989155f4

generated 4.00
keypool keep 3
ERROR: AcceptBlock() : coinbase timestamp is too early
ERROR: ProcessBlock() : AcceptBlock FAILED
ERROR: CheckWork() : ProcessBlock, block not accepted
keypool reserve 4

What does this mean? My guess is that my computer managed to find a new block, but it then failed to broadcast it to the network (I did not manage to mine any coins so far). Anyone knows why it fails?

you can find the debug log under Debug window->Information->Debug log file: open

kurret

member

Activity: 91

Merit: 10

Quote from: Sagemark on September 01, 2017, 10:06:30 PM

Quote from: kurret on September 01, 2017, 06:09:19 PM

Been mining for hours, no coins. This does not seem to be very profitable, 4 ODN is what..1 dollar?

This is a Proof of Stake, not Proof of Work. It's not meant to be mined and mining will end by tomorrow.

Yes I am aware of this, I did not mean it as an attack on the coin overall, just a comment about the initial mining procedure.

andro hac

sr. member

Activity: 574

Merit: 254

Quote from: Sagemark on September 01, 2017, 10:06:30 PM

Quote from: kurret on September 01, 2017, 06:09:19 PM

Been mining for hours, no coins. This does not seem to be very profitable, 4 ODN is what..1 dollar?

This is a Proof of Stake, not Proof of Work. It's not meant to be mined and mining will end by tomorrow.

it is likely that it may end today,11509 blocks Cheesy

andro hac

sr. member

Activity: 574

Merit: 254

Quote from: Zero1One0 on September 01, 2017, 08:51:17 PM

I got my first mine after more than 24 hours. It's a lottery. No one knows who will get the next block as there is no mining pool.

I agree-it's a lottery Grin

Sagemark

full member

Activity: 131

Merit: 100

Quote from: kurret on September 01, 2017, 06:09:19 PM

Been mining for hours, no coins. This does not seem to be very profitable, 4 ODN is what..1 dollar?

This is a Proof of Stake, not Proof of Work. It's not meant to be mined and mining will end by tomorrow.

Zero1One0

full member

Activity: 625

Merit: 125

I got my first mine after more than 24 hours. It's a lottery. No one knows who will get the next block as there is no mining pool.

kurret

member

Activity: 91

Merit: 10

Been mining for hours, no coins. This does not seem to be very profitable, 4 ODN is what..1 dollar?

crpt777

newbie

Activity: 36

Merit: 0

Please, everyone vote for Stratis. Need add Stratis to the Binance exchange

https://www.binance.com/vote.html

If stratis win, OBSIDIAN will win to!

9ndshvb

member

Activity: 86

Merit: 10

Quote from: sxafir on September 01, 2017, 10:15:32 AM

When i can withdraw obsidian from ico page?

When the wallets are ready . .

We will get an email.

sxafir

hero member

Activity: 1022

Merit: 500

When i can withdraw obsidian from ico page?

junglist.massive

hero member

Activity: 759

Merit: 500

cant wait to use it. We should hit status marketcap easy this year

doopie

newbie

Activity: 57

Merit: 0

https://drive.google.com/file/d/0B5ffnLUWqKkMMG1YTXUtNjNvOGc/view

"The current estimate from our developers of the number
of coins required is 10,000 ODN,"

Filmmmakerr

sr. member

Activity: 518

Merit: 251

Hello. Bye.

How much was ico price and how many coins needed for master node?

Topic: Obsidian ODN - CryptoCurrency & Secure Anonymous Messaging - page 49. (Read 92754 times)