[UNO] Unobtanium Info & Discussion - Merge Mine w/BTC! - Update NOW to qt 0.11.5

[cragv]

Better don't send coins right now. We need everyone on the same chain. Hope we get this sorted out quickly. Where is the compiled new wallet?

This appears to be a critical issue, if we're understanding/interpreting correctly. Quoting the above for emphasis!

[edgar]

40 UNO sent earlier has not arrived.

awaiting txid/confirmation but its been 5-6 hrs.


i was under the impression that implementing merge mining was not an actual fork

[FallingKnife]

Messages are out to Bryce.

The suggestion not to move coins for the moment is a good one. Sit tight.

[tuaris]

I am confused what has happened with this blockchain?
The forum says the latest version is 0.9.5.  I am on 0.9.5.9

Code:

Array
(
    [version] => 90509
    [protocolversion] => 70001
    [walletversion] => 60000
    [balance] => 7.02847527
    [blocks] => 600540
    [timeoffset] => 0
    [connections] => 3
    [proxy] => 
    [difficulty] => 544065.74668734
    [testnet] => 
    [keypoololdest] => 1430870554
    [keypoolsize] => 101
    [paytxfee] => 0
    [errors] => Warning: This version is obsolete, upgrade required!
)

Are my miners wasting their time?

[balu2]

I am confused what has happened with this blockchain?
The forum says the latest version is 0.9.5.  I am on 0.9.5.9

Code:

Array
(
    [version] => 90509
    [protocolversion] => 70001
    [walletversion] => 60000
    [balance] => 7.02847527
    [blocks] => 600540
    [timeoffset] => 0
    [connections] => 3
    [proxy] => 
    [difficulty] => 544065.74668734
    [testnet] => 
    [keypoololdest] => 1430870554
    [keypoolsize] => 101
    [paytxfee] => 0
    [errors] => Warning: This version is obsolete, upgrade required!
)

Are my miners wasting their time?

Your version is what the majority of the network is on actually. I think there were some false assumptions by the dev about the recent update. As far as i can see the update of only parts of the network to 0.1 is causing trouble. Stupid mistake, really. I'd recommend to keep an eye out for any new updates here on that matter. Wether hash is wasted isn't quite clear yet. We're waiting for updates from the dev for now.

[tuaris]

I am confused what has happened with this blockchain?
The forum says the latest version is 0.9.5.  I am on 0.9.5.9

Code:

Array
(
    [version] => 90509
    [protocolversion] => 70001
    [walletversion] => 60000
    [balance] => 7.02847527
    [blocks] => 600540
    [timeoffset] => 0
    [connections] => 3
    [proxy] => 
    [difficulty] => 544065.74668734
    [testnet] => 
    [keypoololdest] => 1430870554
    [keypoolsize] => 101
    [paytxfee] => 0
    [errors] => Warning: This version is obsolete, upgrade required!
)

Are my miners wasting their time?

Your version is what the majority of the network is on actually. I think there were some false assumptions by the dev about the recent update. As far as i can see the update of only parts of the network to 0.1 is causing trouble. Stupid mistake, really. I'd recommend to keep an eye out for any new updates here on that matter. Wether hash is wasted isn't quite clear yet. We're waiting for updates from the dev for now.

Thank you for the clarification.  I did a test build of the latest source on Github and it seems as if MM was not supposed to be started quite yet

Code:

Unobtanium Core version v0.10.0.0-d21fb40-dirty-preMM (64-bit)

This is why I always use 'official' releases and never use the latest source.

[FallingKnife]

Bryce replied and asks the following:

All miners update to 0.1.0,   https://github.com/unobtanium-official/Unobtanium

If you are mining on Windows/solo mining with 0.9.5 client, stop.

[Jelks]

40 UNO sent earlier has not arrived.

awaiting txid/confirmation but its been 5-6 hrs.

i was under the impression that implementing merge mining was not an actual fork

Interesting. My 2 S3's, both still mining at MiningPools.tk, are still shipping stuff into my 0.95 wallet as I type this.

However, a small test buy at Bleutrade and then withdrawn a couple of hours ago has still not yet shown up...

[FallingKnife]

If you are mining, notify your pool to upgrade to 0.1.0 by compiling from https://github.com/unobtanium-official/Unobtanium

Then, please let me know which pool you notified so I can take them off my list.

[tertius993]

Bryce replied and asks the following:

All miners update to 0.1.0,   https://github.com/unobtanium-official/Unobtanium

If you are mining on Windows/solo mining with 0.9.5 client, stop.

Can we continue to use 0.9.5 wallets as, well, wallets or should those also be upgraded?

[ethought]

Updated BlockTree.io to 0.1.0

and added peer info page:

http://www.blocktree.io/peers/UNO/

[tuaris]

I will update, but what of all the blocks that have been mined by my pool since?

[balu2]

If you are mining, notify your pool to upgrade to 0.1.0 by compiling from https://github.com/unobtanium-official/Unobtanium

Then, please let me know which pool you notified so I can take them of my list.

Sure, but users will continue to have trouble won't they? If i left my client on for long times in the past i could be a full node, couldn't i?
How do i get my 0.9.5 wallet on the correct block count now? (I'm still 40 blocks behind)

[FallingKnife]

0.1.0 is the correct fork, as shown on https://chainz.cryptoid.info/uno/

For the time being, Windows users please close your 0.9.5 wallets as we push through this.

[FallingKnife]

I will update, but what of all the blocks that have been mined by my pool since?

Thank you ethought,

Tauris after you update, pls post pool details and I will send you some hash.

Solo miners on Windows, please stop for now -- you're on the wrong chain.

Miners, please ask your pools if they are updated to 0.1.0. 
It may be smart to just stop mining for now until we are sure your pool is 0.1.0.

[IMZ]

Have closed my wallet -- windows oh nine oh

Back at dawn, in a few hours

[cryptapus]

I don't think this should be isolated to miners. I believe all transactions on v0.9.5 after block 600k will be questionable at best, on a forked chain at worst. I would advise saving your wallet.dat and waiting for a v0.10 binary to become available.

[FallingKnife]

I don't think this should be isolated to miners. I believe all transactions on v0.9.5 after block 600k will be questionable at best, on a forked chain at worst. I would advise saving your wallet.dat and waiting for a v0.10 binary to become available.

I agree. Its a good time to step back.
Exchanges have been notified. I reached out to known pools in the OP; I'm sure I missed some, so please help with this by contacting your favorite pool and asking them to update to 0.1.0.

[tuaris]

I don't think this should be isolated to miners. I believe all transactions on v0.9.5 after block 600k will be questionable at best, on a forked chain at worst. I would advise saving your wallet.dat and waiting for a v0.10 binary to become available.

I agree. Its a good time to step back.
Exchanges have been notified. I reached out to known pools in the OP; I'm sure I missed some, so please help with this by contacting your favorite pool and asking them to update to 0.1.0.

There was one surprise in this update regarding the daemon version.

Code:

Error: There is no RPC client functionality in bitcoind anymore. Use the bitcoin-cli utility instead.

Had to rework my start-up scripts because of that.

Updates for the FreeBSD port are committed.
https://github.com/tuaris/FreeBSD-Coin-Ports/tree/master/ports/unobtanium

Pool has also been updated to 0.10.0.0
http://mining.securepayment.cc/pools/unobtanium/

It's currently re-indexing.  I will post again when that has completed.

[ipominer]

I don't think this should be isolated to miners. I believe all transactions on v0.9.5 after block 600k will be questionable at best, on a forked chain at worst. I would advise saving your wallet.dat and waiting for a v0.10 binary to become available.

I agree. Its a good time to step back.
Exchanges have been notified. I reached out to known pools in the OP; I'm sure I missed some, so please help with this by contacting your favorite pool and asking them to update to 0.1.0.

ipoMiner has updated to v0.1.0 now. Some form of proactive notice for pools and exchanges would have been nice...

There's definitely a fork that has happened at or around block 600k.