Bump, still no progress from the pools listed below. All others have upgraded and are safe to mine on. Also, if you get this message when running bitmonerod: Last scheduled hard fork time shows a daemon update is needed now You can safely ignore that as long as you are on any Hydrogen Helix version (i.e. 0.9.x). I urge community members to please send a mail as well to the pools listed in my previous comment urging them to upgrade. Any Hydrogen Helix version is fine (0.9.x). Alternatively, miners should move their hash away from it and go to a pool that has already upgraded. A list of pools can be found here: https://monerohash.com/#networkBump, none of the pools listed below 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, still no progress from the pools listed below. All others have upgraded and are safe to mine on. Also, if you get this message when running bitmonerod: Last scheduled hard fork time shows a daemon update is needed now You can safely ignore that as long as you are on any Hydrogen Helix version (i.e. 0.9.x). I urge community members to please send a mail as well to the pools listed in my previous comment urging them to upgrade. Any Hydrogen Helix version is fine (0.9.x). Alternatively, miners should move their hash away from it and go to a pool that has already upgraded. A list of pools can be found here: https://monerohash.com/#networkBump, none of the pools listed below 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. |
|
|
|
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? |
|
|
|
What I find curious is the recent higher number of transactions. I wonder if these coins are mainly going or coming from the exchanges.
What about xmr.to usage? |
|
|
|
Hi guys I am a noob but I have monero in an old wallet from 8.3.3
I have my keys file and address file and password as well. can anyone please instruct me on how to import them into the new wallet
To expand on smooth. Make sure that if you upgrade, you upgrade on the same OS as where you made that old wallet. That is, if you made the wallet on Windows, you should download the Windows binaries and upgrade the wallet on Windows. Cross-sectional OS upgrading doesn't work as far as I know. |
|
|
|
Lending rates (to short) up to 0.2% now.
0.5% currently, this could turn out in an epic short squeeze. EDIT: 1.0% EDIT2: 2% now, insane. 3-4% now. That wall @ 331k is a huge short. |
|
|
|
Bump, http://monero.miner.center/ has upgraded to the proper version. Still no progress from the other pools listed below. All others have upgraded and are safe to mine on. List of pools that haven't upgraded yet: Especially considering the hashrate of minergate.com, I think it is highly irresponsible and unprofessional behavior to not upgrade (or hopefully upgrade very last minute). If you are mining there I would move to a pool that acts professionally and actually cares about the Monero network. Ugh. Can someone that does social media contact them? They have links on their website, bottom right corner: - https://twitter.com/MinerGate- https://www.facebook.com/minergate/They were already contacted by the official twitter account a few days ago, see: https://twitter.com/MinerGate/status/710727384136335361But would be good if others contact them too. |
|
|
|
Lending rates (to short) up to 0.2% now.
0.5% currently, this could turn out in an epic short squeeze. EDIT: 1.0% EDIT2: 2% now, insane. |
|
|
|
Bump, http://monero.miner.center/ has upgraded to the proper version. Still no progress from the other pools listed below. All others have upgraded and are safe to mine on. I urge community members to please send a mail as well to the pools listed in my previous comment urging them to upgrade. Any Hydrogen Helix version is fine (0.9.x). Alternatively, miners should move their hash away from it and go to a pool that has already upgraded. A list of pools can be found here: https://monerohash.com/#networkBump, none of the pools listed below 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, http://monero.miner.center/ has upgraded to the proper version. Still no progress from the other pools listed below. All others have upgraded and are safe to mine on. I urge community members to please send a mail as well to the pools listed in my previous comment urging them to upgrade. Any Hydrogen Helix version is fine (0.9.x). Alternatively, miners should move their hash away from it and go to a pool that has already upgraded. A list of pools can be found here: https://monerohash.com/#networkBump, none of the pools listed below 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. |
|
|
|
|
Lending rates (to short) up to 0.2% now.
|
|
|
|
They run a liquidation algorithm that is supposed to prevent flashcrashes which could result in "socialized losses".
And how would we even know if they did that or have not already done it? I am not sure I understand your question here, could you clarify? We have no means of detecting whether it is a Bucket Shop or not. You simply borrow from lenders that have offered their BTC against a certain rate. What I meant with "They run a liquidation algorithm that is supposed to prevent flashcrashes which could result in "socialized losses" is that there is a delay in liquidation if the bids drop too fast (afaik). Due to the delay the bids have some time to replenish again and this system prevents too deep flashcrashes. An example would be the flashcrash to around 100$ they had in 2014. |
|
|
|
Lately, the jumps come on Wednesdays and weekends. I had to say this publicly in order to break the chain.
Chaos theory can be a bitch sometimes. |
|
|
|
I just updated to this brand new simplewallet. https://github.com/monero-project/bitmonero/releases/tag/v0.9.2Simplewallet can be used to make an ordinary wallet. The way that simplewallet itself creates mnemonic seed, address, spendkey and viewkey. Simplewallet can be used to make an ordidinary wallet by already known address, spendkey and viewkey. Simplewallet can be used to make a view-only-wallet by allready known address and viewkey. How simplewallet can be used to make an ordinary wallet by already known mnemonic seed? You can restore the seed, which will create a new wallet. Subsequently if that new wallet is created you can extract the spendkey and viewkey from it. |
|
|
|
"The Secret Behind CryptoWall’s Success" (the ransomware)http://www.imperva.com/docs/IMPERVA_HII_CryptoWall_report.pdf1.1 Key Findings
1. CryptoWall 3.0 payment infrastructure can be traced
a. Bitcoin wallet analysis can be done to trace the cyber criminals profiting from the ransomware The tracking Bitcoin part starts from page 8. EDIT: Most striking figure in my opinion: 
|
|
|
|
"The Secret Behind CryptoWall’s Success" (the ransomware)http://www.imperva.com/docs/IMPERVA_HII_CryptoWall_report.pdf1.1 Key Findings
1. CryptoWall 3.0 payment infrastructure can be traced
a. Bitcoin wallet analysis can be done to trace the cyber criminals profiting from the ransomware The tracking Bitcoin part starts from page 8. EDIT: Most striking figure in my opinion:
|
|
|
|
|
Show Posts
