Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 623. (Read 4671953 times)
Will MyMonero.com be up on tomorrow 25. March 06.00 GMT?
I'm wondering why block time was increased, where can I read about it?
There is a thread with the proposal and discussion:
https://forum.getmonero.org/20/general-discussion/2401/increasing-the-block-time
Crosspost from the speculation thread...
Monero added to Microsoft Azure Blockchain as a service:
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
Official link:
https://azure.microsoft.com/en-us/blog/azure-blockchain-update-7/
The "try it out here" link from official MS Azure blog is broken (404 Page not found).
https://azure.microsoft.com/en-us/documentation/templates/monero-on-ubuntu/
Same with this one:
https://azure.microsoft.com/en-us/documentation/templates/ethereum-cpp-on-ubuntu/
I'll forward it to fluffypony.
Can someone explain the Azure news? I am a bit perplexed by what this could mean.
Thx in advance,
Its about sharing
It basically means at this point that there is a template that can get a Monero node running on Azure quickly and easily. So pretty bare-bones right now. It could do other things in the future.
I'm wondering why block time was increased, where can I read about it?
Its been discussed elsewhere, but I'm not sure there's a cogent document about it. Basically, the 1 minute blocktime was put into place by the original developer, thankful for today, when he cloned bytecoin to create bitmonero. If you don't know the rest of the story, the current core team then forked bitmonero to create the chain we know and love today as Monero. If you dive into the historical posts, you can see the disagreement with 1 min vs 2 minute blocktimes, and the post-hoc rationale provided by TFT was that 1 minute blocktimes would increase distribution in the initial phase (more block finders would be solo miners etc), though its probably he wanted 1 minute blocks because short blocks were all the rage in 2014. And it was also put forward that the chain would switch to 2 minute blocks once the primary distribution was over, in order to prevent re-orgs (when presumably the blocks would be bigger later in the chain's life).
So in short, the blocktime was increased to prevent high frequency of reorganizations.
It also lessens the slow-to-verify POW impact (which positively impacts orphans somewhat, but more so initial/catchup syncs). 1 minute blocks are on the dangerously short side for a decentralized POW currency, in my opinion.
Crosspost from the speculation thread...
Monero added to Microsoft Azure Blockchain as a service:
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
Official link:
https://azure.microsoft.com/en-us/blog/azure-blockchain-update-7/
The "try it out here" link from official MS Azure blog is broken (404 Page not found).
https://azure.microsoft.com/en-us/documentation/templates/monero-on-ubuntu/
Same with this one:
https://azure.microsoft.com/en-us/documentation/templates/ethereum-cpp-on-ubuntu/
I'll forward it to fluffypony.
Can someone explain the Azure news? I am a bit perplexed by what this could mean.
Thx in advance,
Its about sharing
I'm wondering why block time was increased, where can I read about it?
Its been discussed elsewhere, but I'm not sure there's a cogent document about it. Basically, the 1 minute blocktime was put into place by the original developer, thankful for today, when he cloned bytecoin to create bitmonero. If you don't know the rest of the story, the current core team then forked bitmonero to create the chain we know and love today as Monero. If you dive into the historical posts, you can see the disagreement with 1 min vs 2 minute blocktimes, and the post-hoc rationale provided by TFT was that 1 minute blocktimes would increase distribution in the initial phase (more block finders would be solo miners etc), though its probably he wanted 1 minute blocks because short blocks were all the rage in 2014. And it was also put forward that the chain would switch to 2 minute blocks once the primary distribution was over, in order to prevent re-orgs (when presumably the blocks would be bigger later in the chain's life).
So in short, the blocktime was increased to prevent high frequency of reorganizations.
Off the top of my head, block time was increased from 1 to 2 minutes to reduce the number of empty blocks, and also to reduce the number of orphan blocks.
I'm wondering why block time was increased, where can I read about it?
Crosspost from the speculation thread...
Monero added to Microsoft Azure Blockchain as a service:
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
Official link:
https://azure.microsoft.com/en-us/blog/azure-blockchain-update-7/
The "try it out here" link from official MS Azure blog is broken (404 Page not found).
https://azure.microsoft.com/en-us/documentation/templates/monero-on-ubuntu/
Same with this one:
https://azure.microsoft.com/en-us/documentation/templates/ethereum-cpp-on-ubuntu/
I'll forward it to fluffypony.
Crosspost from the speculation thread...
Monero added to Microsoft Azure Blockchain as a service:
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
Official link:
https://azure.microsoft.com/en-us/blog/azure-blockchain-update-7/
The "try it out here" link from official MS Azure blog is broken (404 Page not found).
https://azure.microsoft.com/en-us/documentation/templates/monero-on-ubuntu/
Crosspost from the speculation thread...
Monero added to Microsoft Azure Blockchain as a service:
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
Official link:
https://azure.microsoft.com/en-us/blog/azure-blockchain-update-7/
Very nice!
Who should we credit for the text on Monero there? It seems pretty well researched.
Fluffypony :-)
Crosspost from the speculation thread...
Monero added to Microsoft Azure Blockchain as a service:
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
Official link:
https://azure.microsoft.com/en-us/blog/azure-blockchain-update-7/
Very nice!
Who should we credit for the text on Monero there? It seems pretty well researched.
Crosspost from the speculation thread...
Monero added to Microsoft Azure Blockchain as a service:
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
Official link:
https://azure.microsoft.com/en-us/blog/azure-blockchain-update-7/
My god can we find a block already on Monerohash.com Long wait since the fork.
Crosspost from the speculation thread...
Monero added to Microsoft Azure Blockchain as a service:
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
https://hellomonero.com/article/monero-added-microsofts-azure-blockchain-service
use transfer 0 for 200xmr to poloniex.com ,fee is 0.4 xmr,does that too high?
Where are you sending from? The default fee is 0.01 XMR per KB. It could very well be that you have a lot of dust in your wallet. Did you mine to it?
Are you sending from simplewallet or from a pool directly? That fee looks way too high for simplewallet and the transaction will likely not go through if it is send from simplewallet because it is above the median and therefore miners will incur a penalty to include your transaction in the block. Like papa_lazzarou said, if you are sending from simplewallet, try to "undust" your dust with the sweep_dust function first. You should not have any issue transfering Monero thereafter.
Error: not enough money to transfer, available only 0.179658438977, transaction amount 0.380000000000 = 0.190000000000 + 0.190000000000 (fee)
i used the command sweep_dust got this error
What are coinbase transactions?
That's another term for mining.
Bear in mind that Zcash's math also is supposed to ensure that every transaction has outputs = inputs. The main differences are:
1. The RingCT math is orders of magnitude simpler. I can almost understand it, and that's saying a fair amount (not a cryptographer).
2. Zcash has the trusted setup which, if compromised in any way, will allow coins to be created without any possibility of detection. RingCT has no trusted setup.
I'm pretty sure with zcash that you can't even tell how many coins are in circulation. So you can make a rough estimate based on the emission curve but there is no way to know how many coins have been mined. Paired with the trusted setup this is pretty risky. RingCT doesn't have a trusted setup but once it's implemented will we still be able to see how many monero are in circulation? Or will you be unable to monitor total money supply?
I received a reply from cryptonotepool.org.uk today (from my email 5 days ago) saying they may look into upgrading this weekend. It didn't sound very definite though.
Update, all pending pools have either upgraded or found a block.
Pools that found a V2 block so far (and are thus safe to mine on):
https://moneropool.com/
http://monero.crypto-pool.fr/
http://dwarfpool.com/xmr
http://xmr.alimabi.cn/
https://minergate.com/pool-stats/mro
http://mro.poolto.be/#pool_blocks
https://monerohash.com/#pool_blocks
http://minexmr.com/#pool_blocks
http://xmr.prohash.net/#pool_blocks
http://monero.miner.center/#pool_blocks
http://mro.poolto.be/#pool_blocks
http://monero.xminingpool.com/#pool_blocks
Pending (i.e. where on the right version before the fork, but haven't found a block yet):
https://monerohash.com/#pool_blocks
http://minexmr.com/#pool_blocks (found the fork block, but nothing after)
http://xmr.prohash.net/#pool_blocks
http://monero.miner.center/#pool_blocks
http://mro.poolto.be/#pool_blocks (seems offline currently)
http://monero.xminingpool.com/#pool_blocks
Wrong chain (i.e. where on the wrong version before the fork):
http://cryptmonero.com/#pool_blocks <= Botnet probably, see:
http://cryptonotepool.org.uk/#pool_blocks (indicated they would upgrade though)
If you are on a private pool, please check if your pool is finding blocks after 1009827. Pending pools probably got stuck due to their (custom) pool software. Issue reported by primer-:
https://moneropool.com/
http://monero.crypto-pool.fr/
http://dwarfpool.com/xmr
http://xmr.alimabi.cn/
https://minergate.com/pool-stats/mro
http://mro.poolto.be/#pool_blocks
https://monerohash.com/#pool_blocks
http://minexmr.com/#pool_blocks
http://xmr.prohash.net/#pool_blocks
http://monero.miner.center/#pool_blocks
http://mro.poolto.be/#pool_blocks
http://monero.xminingpool.com/#pool_blocks
Pending (i.e. where on the right version before the fork, but haven't found a block yet):
http://minexmr.com/#pool_blocks (found the fork block, but nothing after)
http://xmr.prohash.net/#pool_blocks
http://monero.miner.center/#pool_blocks
http://mro.poolto.be/#pool_blocks (seems offline currently)
http://monero.xminingpool.com/#pool_blocks
Wrong chain (i.e. where on the wrong version before the fork):
http://cryptmonero.com/#pool_blocks <= Botnet probably, see:
Quote
Seems to be mainly a botnet: http://fpaste.org/321343/14552121/. Also, reported number of miners seems fake if you compare it to the number of paid miners.
http://cryptonotepool.org.uk/#pool_blocks (indicated they would upgrade though)
If you are on a private pool, please check if your pool is finding blocks after 1009827. Pending pools probably got stuck due to their (custom) pool software. Issue reported by primer-:
Quote
"Error: Failed to parse block
at Object.BlockTemplate.nextBlob (/root/test/cryptonote-universal-pool/lib/pool.js:120:23)
at Object.Miner.getJob (/root/test/cryptonote-universal-pool/lib/pool.js:297:41)
at handleMinerMethod (/root/test/cryptonote-universal-pool/lib/pool.js:492:28)
at handleMessage (/root/test/cryptonote-universal-pool/lib/pool.js:606:13)
at Socket.socket.on.on.on.pushMessage (/root/test/cryptonote-universal-pool/lib/pool.js:660:25)
at Socket.EventEmitter.emit (events.js:95:17)
at Socket. (_stream_readable.js:746:14)
at Socket.EventEmitter.emit (events.js:92:17)
at emitReadable_ (_stream_readable.js:408:10)
at emitReadable (_stream_readable.js:404:5)
cryptonote-universal-pool wont run after the fork. node-cryptonote-pool works just fine
at Object.BlockTemplate.nextBlob (/root/test/cryptonote-universal-pool/lib/pool.js:120:23)
at Object.Miner.getJob (/root/test/cryptonote-universal-pool/lib/pool.js:297:41)
at handleMinerMethod (/root/test/cryptonote-universal-pool/lib/pool.js:492:28)
at handleMessage (/root/test/cryptonote-universal-pool/lib/pool.js:606:13)
at Socket.socket.on.on.on.pushMessage (/root/test/cryptonote-universal-pool/lib/pool.js:660:25)
at Socket.EventEmitter.emit (events.js:95:17)
at Socket.
at Socket.EventEmitter.emit (events.js:92:17)
at emitReadable_ (_stream_readable.js:408:10)
at emitReadable (_stream_readable.js:404:5)
cryptonote-universal-pool wont run after the fork. node-cryptonote-pool works just fine
So net hash dropped because of botnets gone after fork? Can it be the reason?
I know for certain that at least 600 KH/s of botnet dropped off. We have to see in a few days what really dropped off, likely botnets as you state.
Jump to: