Bump, none of the pools have upgraded yet. To clarify this, you meant that none of the unupgraded pools have upgraded since your previous post. In fact most of the pools already upgraded some time ago. Yes, thanks for clarifying my comment. I'll post a more clarifying comment in my bump post tomorrow. |
|
|
|
Bump, none of the pools have upgraded yet. However, Minergate said they will upgrade soon, see: https://twitter.com/MinerGate/status/710727384136335361PSA: Users, (solo)miners, exchanges/merchants, and pooloperators must be on 0.9.x (preferably 0.9.2) in advance of the hardfork otherwise you will get forked/booted off the network. If you are mining on one of the following pools, please contact your poolop immediately or switch to another pool.
Approximately the 23th of March there will be a hardfork on the Monero network. Most pools have upgraded, but some have not yet. If they don't upgrade before the hardfork they will get forked/booted off the network. As a result you will miss out on revenue if you are mining on these pools. Thus, if you are mining on the following pools, please contact your pool owner as soon as possible and urge them to upgrade. Alternatively, you can switch to a pool that is on the right version. FYI: You can plug the blockheader of your pool into " http://moneroblocks.info/api/get_block_header/hash_of_blockheader". The minor_version must show "minor_version: 2". This means that the pool is on the right version. If it shows "0" or "1" the pool is on an outdated version. An example of a pool on the right version (Monerohash): http://moneroblocks.info/api/get_block_header/2a88740443bf654e595bba7061509e6a3a80623da5de2478c4a90b45454a7fa8List of pools that haven't upgraded yet: List of pools that have upgraded:You can find most pools here: https://monerohash.com/#networkSome of the aforementioned pools are listed there as well. If you are switching, avoid the aforementioned pools.
Binaries:Monero v0.9.2 - Hydrogen Helix - released! (Urgent and important bug fixes for the upcoming hard fork)https://github.com/monero-project/bitmonero/releases/tag/v0.9.2<fluffypony> will do shasums / gpg signed mesage tomorrow Information from Github: This has urgent and important bug fixes to 0.9.0 Hydrogen Helix - Major performance and size improvements to the LMDB database implementation
- Urgent and important bug fixes for the upcoming hard fork
- Huge bug fixes to the database hard fork handling
- New simplewallet flag to restore from keys
- Initial work on a wallet library / API
- Updated in-source block headers
General hardfork information:Background: https://forum.getmonero.org/4/academic-and-technical/303/a-formal-approach-towards-better-hard-fork-managementWhat are the change(s) with the upcoming hard fork on the 20th of March? - Blocktime is bumped from 1 to 2 minutes. See:
https://forum.getmonero.org/20/general-discussion/2401/increasing-the-block-time- Minimum blocksize is bumped to 60 KB. See:
https://forum.getmonero.org/20/general-discussion/2409/increasing-the-minimum-block-sizeA big advantage of this is that current individual transactions that sometimes won't go through (because they are a bit above the median due to many outputs (e.g. dust), or the daemon / MyMonero rejects them for some reason) can easily be included in the block without incurring a penalty. Above is a bit of a blunt explanation, I am sure one of the core-team members / developers could give you a more detailed explanation. - Finally, the recommendations from the MRL team stated in MRL-0004, of which the minimum mixin >= 3 is probably the most salient. See:
https://lab.getmonero.org/pubs/MRL-0004.pdfP.S. Due to variance the hard fork will likely be on the 21th or 22th of March. A specific block height was determined for the hardfork, not a specific date. The specific blockheight for the hardfork can be found here: https://github.com/monero-project/bitmonero/blob/master/src/cryptonote_core/blockchain.cpp#L83// version 2 starts from block 1009827 P.P.S. As long as you are on any 0.9.x version in advance of the hardfork you are fine. |
|
|
|
Bump, none of the pools have upgraded yet. However, Minergate said they will upgrade soon, see: https://twitter.com/MinerGate/status/710727384136335361PSA: Users, (solo)miners, exchanges/merchants, and pooloperators must be on 0.9.x (preferably 0.9.2) in advance of the hardfork otherwise you will get forked/booted off the network. If you are mining on one of the following pools, please contact your poolop immediately or switch to another pool.
Approximately the 23th of March there will be a hardfork on the Monero network. Most pools have upgraded, but some have not yet. If they don't upgrade before the hardfork they will get forked/booted off the network. As a result you will miss out on revenue if you are mining on these pools. Thus, if you are mining on the following pools, please contact your pool owner as soon as possible and urge them to upgrade. Alternatively, you can switch to a pool that is on the right version. FYI: You can plug the blockheader of your pool into " http://moneroblocks.info/api/get_block_header/hash_of_blockheader". The minor_version must show "minor_version: 2". This means that the pool is on the right version. If it shows "0" or "1" the pool is on an outdated version. An example of a pool on the right version (Monerohash): http://moneroblocks.info/api/get_block_header/2a88740443bf654e595bba7061509e6a3a80623da5de2478c4a90b45454a7fa8List of pools that haven't upgraded yet: List of pools that have upgraded:You can find most pools here: https://monerohash.com/#networkSome of the aforementioned pools are listed there as well. If you are switching, avoid the aforementioned pools.
Binaries:Monero v0.9.2 - Hydrogen Helix - released! (Urgent and important bug fixes for the upcoming hard fork)https://github.com/monero-project/bitmonero/releases/tag/v0.9.2<fluffypony> will do shasums / gpg signed mesage tomorrow Information from Github: This has urgent and important bug fixes to 0.9.0 Hydrogen Helix - Major performance and size improvements to the LMDB database implementation
- Urgent and important bug fixes for the upcoming hard fork
- Huge bug fixes to the database hard fork handling
- New simplewallet flag to restore from keys
- Initial work on a wallet library / API
- Updated in-source block headers
General hardfork information:Background: https://forum.getmonero.org/4/academic-and-technical/303/a-formal-approach-towards-better-hard-fork-managementWhat are the change(s) with the upcoming hard fork on the 20th of March? - Blocktime is bumped from 1 to 2 minutes. See:
https://forum.getmonero.org/20/general-discussion/2401/increasing-the-block-time- Minimum blocksize is bumped to 60 KB. See:
https://forum.getmonero.org/20/general-discussion/2409/increasing-the-minimum-block-sizeA big advantage of this is that current individual transactions that sometimes won't go through (because they are a bit above the median due to many outputs (e.g. dust), or the daemon / MyMonero rejects them for some reason) can easily be included in the block without incurring a penalty. Above is a bit of a blunt explanation, I am sure one of the core-team members / developers could give you a more detailed explanation. - Finally, the recommendations from the MRL team stated in MRL-0004, of which the minimum mixin >= 3 is probably the most salient. See:
https://lab.getmonero.org/pubs/MRL-0004.pdfP.S. Due to variance the hard fork will likely be on the 21th or 22th of March. A specific block height was determined for the hardfork, not a specific date. The specific blockheight for the hardfork can be found here: https://github.com/monero-project/bitmonero/blob/master/src/cryptonote_core/blockchain.cpp#L83// version 2 starts from block 1009827 P.P.S. As long as you are on any 0.9.x version in advance of the hardfork you are fine. |
|
|
|
Please explain very simply what is needed Hydrogen Helix? Thanks.
Yes, any version of Hydrogen Helix (0.9.x) is fine, but preferably 0.9.2 |
|
|
|
When will 0.9.2 be available on getmonero.org for Windows 64 bit? Special thanks to osensei for already updating Monerohash.com. Mining shall continue uninterrupted  Probably tomorrow when Fluffypony GPG signed the binaries (and published the checksums). |
|
|
|
PSA: Users, (solo)miners, exchanges/merchants, and pooloperators must be on 0.9.x (preferably 0.9.2) in advance of the hardfork otherwise you will get forked/booted off the network. If you are mining on one of the following pools, please contact your poolop immediately or switch to another pool.List of pools that haven't upgraded yet: I use the cryptonotepool because it supports the devs, but they have low hashrate. OTOH Minergate is ~1/14 of the network! If they are the go-to pool for bot herders (nice web miner!) it will be interesting to see if it stops the dumping, as GPU hoarders take over their absent portion of the global hashrate. Minergate kind of confirmed to the core-team they would upgrade before the hardfork. However, until they really have upgraded I'll include them into the PSA. If pools upgrade I'll take them out of the PSA. |
|
|
|
PSA: Users, (solo)miners, exchanges/merchants, and pooloperators must be on 0.9.x (preferably 0.9.2) in advance of the hardfork otherwise you will get forked/booted off the network. If you are mining on one of the following pools, please contact your poolop immediately or switch to another pool.
Approximately the 23th of March there will be a hardfork on the Monero network. Most pools have upgraded, but some have not yet. If they don't upgrade before the hardfork they will get forked/booted off the network. As a result you will miss out on revenue if you are mining on these pools. Thus, if you are mining on the following pools, please contact your pool owner as soon as possible and urge them to upgrade. Alternatively, you can switch to a pool that is on the right version. FYI: You can plug the blockheader of your pool into " http://moneroblocks.info/api/get_block_header/hash_of_blockheader". The minor_version must show "minor_version: 2". This means that the pool is on the right version. If it shows "0" or "1" the pool is on an outdated version. An example of a pool on the right version (Monerohash): http://moneroblocks.info/api/get_block_header/2a88740443bf654e595bba7061509e6a3a80623da5de2478c4a90b45454a7fa8List of pools that haven't upgraded yet: List of pools that have upgraded:You can find most pools here: https://monerohash.com/#networkSome of the aforementioned pools are listed there as well. If you are switching, avoid the aforementioned pools.
Binaries:Monero v0.9.2 - Hydrogen Helix - released! (Urgent and important bug fixes for the upcoming hard fork)https://github.com/monero-project/bitmonero/releases/tag/v0.9.2<fluffypony> will do shasums / gpg signed mesage tomorrow Information from Github: This has urgent and important bug fixes to 0.9.0 Hydrogen Helix - Major performance and size improvements to the LMDB database implementation
- Urgent and important bug fixes for the upcoming hard fork
- Huge bug fixes to the database hard fork handling
- New simplewallet flag to restore from keys
- Initial work on a wallet library / API
- Updated in-source block headers
General hardfork information:Background: https://forum.getmonero.org/4/academic-and-technical/303/a-formal-approach-towards-better-hard-fork-managementWhat are the change(s) with the upcoming hard fork on the 20th of March? - Blocktime is bumped from 1 to 2 minutes. See:
https://forum.getmonero.org/20/general-discussion/2401/increasing-the-block-time- Minimum blocksize is bumped to 60 KB. See:
https://forum.getmonero.org/20/general-discussion/2409/increasing-the-minimum-block-sizeA big advantage of this is that current individual transactions that sometimes won't go through (because they are a bit above the median due to many outputs (e.g. dust), or the daemon / MyMonero rejects them for some reason) can easily be included in the block without incurring a penalty. Above is a bit of a blunt explanation, I am sure one of the core-team members / developers could give you a more detailed explanation. - Finally, the recommendations from the MRL team stated in MRL-0004, of which the minimum mixin >= 3 is probably the most salient. See:
https://lab.getmonero.org/pubs/MRL-0004.pdfP.S. Due to variance the hard fork will likely be on the 21th or 22th of March. A specific block height was determined for the hardfork, not a specific date. The specific blockheight for the hardfork can be found here: https://github.com/monero-project/bitmonero/blob/master/src/cryptonote_core/blockchain.cpp#L83// version 2 starts from block 1009827 P.P.S. As long as you are on any 0.9.x version in advance of the hardfork you are fine.
|
|
|
|
PSA: Users, (solo)miners, exchanges/merchants, and pooloperators must be on 0.9.x (preferably 0.9.2) in advance of the hardfork otherwise you will get forked/booted off the network. If you are mining on one of the following pools, please contact your poolop immediately or switch to another pool.
Approximately the 23th of March there will be a hardfork on the Monero network. Most pools have upgraded, but some have not yet. If they don't upgrade before the hardfork they will get forked/booted off the network. As a result you will miss out on revenue if you are mining on these pools. Thus, if you are mining on the following pools, please contact your pool owner as soon as possible and urge them to upgrade. Alternatively, you can switch to a pool that is on the right version. FYI: You can plug the blockheader of your pool into " http://moneroblocks.info/api/get_block_header/hash_of_blockheader". The minor_version must show "minor_version: 2". This means that the pool is on the right version. If it shows "0" or "1" the pool is on an outdated version. An example of a pool on the right version (Monerohash): http://moneroblocks.info/api/get_block_header/2a88740443bf654e595bba7061509e6a3a80623da5de2478c4a90b45454a7fa8List of pools that haven't upgraded yet: List of pools that have upgraded:You can find most pools here: https://monerohash.com/#networkSome of the aforementioned pools are listed there as well. If you are switching, avoid the aforementioned pools.
Binaries:Monero v0.9.2 - Hydrogen Helix - released! (Urgent and important bug fixes for the upcoming hard fork)https://github.com/monero-project/bitmonero/releases/tag/v0.9.2<fluffypony> will do shasums / gpg signed mesage tomorrow Information from Github: This has urgent and important bug fixes to 0.9.0 Hydrogen Helix - Major performance and size improvements to the LMDB database implementation
- Urgent and important bug fixes for the upcoming hard fork
- Huge bug fixes to the database hard fork handling
- New simplewallet flag to restore from keys
- Initial work on a wallet library / API
- Updated in-source block headers
General hardfork information:Background: https://forum.getmonero.org/4/academic-and-technical/303/a-formal-approach-towards-better-hard-fork-managementWhat are the change(s) with the upcoming hard fork on the 20th of March? - Blocktime is bumped from 1 to 2 minutes. See:
https://forum.getmonero.org/20/general-discussion/2401/increasing-the-block-time- Minimum blocksize is bumped to 60 KB. See:
https://forum.getmonero.org/20/general-discussion/2409/increasing-the-minimum-block-sizeA big advantage of this is that current individual transactions that sometimes won't go through (because they are a bit above the median due to many outputs (e.g. dust), or the daemon / MyMonero rejects them for some reason) can easily be included in the block without incurring a penalty. Above is a bit of a blunt explanation, I am sure one of the core-team members / developers could give you a more detailed explanation. - Finally, the recommendations from the MRL team stated in MRL-0004, of which the minimum mixin >= 3 is probably the most salient. See:
https://lab.getmonero.org/pubs/MRL-0004.pdfP.S. Due to variance the hard fork will likely be on the 21th or 22th of March. A specific block height was determined for the hardfork, not a specific date. The specific blockheight for the hardfork can be found here: https://github.com/monero-project/bitmonero/blob/master/src/cryptonote_core/blockchain.cpp#L83// version 2 starts from block 1009827 P.P.S. As long as you are on any 0.9.x version in advance of the hardfork you are fine.
|
|
|
|
Fluffypony temporarily pointed the getmonero.org downloads back to 0.9.1 because some users were incurring and subsequently reporting errors. This only happened for two guys on Linux when they switched from 0.9.1 to 0.9.2 (the blockchain is compatible, thus no resync is needed). However, syncing from scratch seems to work fine on 0.9.2. I see. Just upgraded these three nodes without any issues from 0.9.1 to 0.9.2: - Windows 7 x64 - Ubuntu 15.10 x64 - Ubuntu 14.04.4 LTS x64 For fresh Linux installations (sync from scratch) are you currently still recommending 0.9.2 over 0.9.1? 0.9.2 certainly. There is some annoying transaction bug in 0.9.1 which gets fixed. EDIT: 0.9.2 binaries (except for linux 32 bit) aren't available on the getmonero.org website because fluffypony hasn't GPG signed them yet. However, you can download them from Github (bear in mind that those aren't signed yet too though). |
|
|
|
Fluffypony temporarily pointed the getmonero.org downloads back to 0.9.1 because some users were incurring and subsequently reporting errors. This only happened for two guys on Linux when they switched from 0.9.1 to 0.9.2 (the blockchain is compatible, thus no resync is needed). However, syncing from scratch seems to work fine on 0.9.2. |
|
|
|
Testing the horizontal support zone again:  Ask side until 275k is relatively flat. |
|
|
|
Is the upgrade available for 32bit linux (ubuntu)?
Not yet, probably soon. |
|
|
|
There's a hard fork in less than a week and no binaries have yet been released ?!
Did you miss this? Also, any 0.9.x version is fine in advance of the hardfork. The first 0.9.x version was released on 31 December 2015. |
|
|
|
If I understood correctly (bear in mind that this rarely happens  ) fluffypony was referring to the possibility of MITM attacks. In part yes, but also malware on your computer. There is no substitute for cold storage, paper wallets, good hardware wallets, etc. So, afaik, there is nothing less secure with the wallets created with mymonero (discounting the 13 vs 24 word mnemonic).
If you, for whatever reason, used mymonero to create a coldish wallet, and never login again, you should be pretty safeish. That is true assuming you are completely sure that nothing was compromised when you created it. Hard to really know that. Well, what I wanted to convey is that, if one has already created the wallet for cold storage in mymonero, either the coins are already gone or they are still there. Therefore, accessing mymonero just to transfer the coins to another cold storage may in fact worsen your chances of getting hacked. It would be safer to wait for the code to restore short mnemonic seeds to be available for offline use. Either through simplewallet or a third party client. I'll just speculate here, but I believe what was ultimately referred to was the vulnerability of MITM when accessing mymonero via Tor because outproxies are essentially just "men in the middle" and anyone using them is trusting that they are benign. I'm pretty sure that if you see the http s in standard clearnet, things are encrypted end to end so noone in the middle can read your stuffs. This doesn't prevent malware on your end from swiping your stuffs though. Keyloggers I guess would be the main thing. Or if your text input into the mymonero login is stored temporarily in any fashion. But ultimately I don't really know what I'm talking about, I'm just piecing together what I've gathered so far. What concerns me is the amount that was stolen. That had to have been one of the larger if not the largest wallet on there. That says to me someone either targeted him specifically or had/has access to that info. I would not consider MyMonero safe for other than pocket change. And expect that someday every one of those accounts will be emptied. The Odds of only his account (specifically such a large one) going through a poison Tor node are So extremely low I can't even entertain the thought of that being the method of compromise. Highly unlikely it was a targeted attack. Also, fairly unlikely that it was a Tor MITM attack. Even if it was, it probably was a driveby attack instead of a targeted one. MyMonero doesn't have a .onion link and therefore it is fairly easy to perform an MITM attack for a tor exit node (I think fluffypony stated that they already had earlier cases of TOR MITM attacks on MyMonero). Same happened to blockchain.info before they had a .onion address. Lots of threads about people that had their BTC stolen. It is more likely malware/trojan/rootkit/virus etc. that somehow stole his XMR, i.e. acquired his seed somehow. |
|
|
|
I am considering getting a Trezor. I have little interest in BTC at the moment (though multi-coin capability may be handy), so this would be based on the expectation that XMR compatible Trezor firmware will be fully functional going forward. Reasonable assumption?
Q
It already works  http://weuse.cash/2016/03/07/trezor-for-monero-first-impressions/Just consider it beta until it's merged with the official Trezor firmware  Yeah, I guess I mean is it a good bet that this will get official. I would be looking to use this for more than testing. Not really sure how bg a deal the viewkey transmission is. Anyway, I prefer the idea of Trezor to paper wallets, so I hope it happens. Thanks to NoodleDoodle for doing the groundwork on this. Q One of the trezor founders was asking for testers, so most likely it gets merged upstream (and thus signed by Trezor) once the code is finalized. See: https://twitter.com/AlenaSatoshi/status/709837766150983680 |
|
|
|
|
Show Posts
