|
It looks to me that his fee is simply higher than the amount of dust and therefore the sweep_dust command doesn't work.
|
|
|
|
We'll soon see if it's sell the news like bitcoin or it's moonero. Next two weeks are critical  I think so its buy or rumor, sell on news thing. But will see. I am a bit baffled how people can think a hardfork is a "buy the rumour, sell the news" event. Probably nothing will happen price wise. |
|
|
|
Bump, still no progress from the pools listed below. Minergate has indicated that they are in the process of upgrading though, see conversations here with the official Monero twitter account: https://twitter.com/MinerGate/with_repliesAll 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 strongly urge every miner that is still mining on one of the pools listed below to move his hash to another pool that has upgraded. A list of pools can be found here: https://monerohash.com/#networkPSA: Users, (solo)miners, exchanges/merchants, and pooloperators must be on 0.9.x (preferably 0.9.3) 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.3 - Hydrogen Helix - released! (Urgent and important bug fixes to 0.9.2 Hydrogen Helix) https://github.com/monero-project/bitmonero/releases/tag/v0.9.3
Information from Github:This has urgent and important bug fixes to 0.9.2 Hydrogen Helix - Urgent bug fix for database corruption issues in 0.9.2
- Official Windows 32-bit releases are back
- Updates to miniupnpc
- Sets v3 fork date for September, 2016
- Fixes core tests and re-enables them
- Fixes a problem with --password-file not working in RPC mode
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. Minergate has indicated that they are in the process of upgrading though, see conversations here with the official Monero twitter account: https://twitter.com/MinerGate/with_repliesAll 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 strongly urge every miner that is still mining on one of the pools listed below to move his hash to another pool that has upgraded. A list of pools can be found here: https://monerohash.com/#networkPSA: Users, (solo)miners, exchanges/merchants, and pooloperators must be on 0.9.x (preferably 0.9.3) 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.3 - Hydrogen Helix - released! (Urgent and important bug fixes to 0.9.2 Hydrogen Helix) https://github.com/monero-project/bitmonero/releases/tag/v0.9.3
Information from Github:This has urgent and important bug fixes to 0.9.2 Hydrogen Helix - Urgent bug fix for database corruption issues in 0.9.2
- Official Windows 32-bit releases are back
- Updates to miniupnpc
- Sets v3 fork date for September, 2016
- Fixes core tests and re-enables them
- Fixes a problem with --password-file not working in RPC mode
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. |
|
|
|
So now that most folks are on 0.9.3 the blocks will come every 2 minutes. Does this mean the reward for mining is now doubled or is the emissions just slowed down now by half? I remember seeing something about this months back but don't have the time to comb through all the posts on this thread. Any info is appreciated. My wording may not be the best here but I think most of you will get what I'm asking.
The block reward is doubled such that the reward per minute remains the same. |
|
|
|
I like Shen's papers more than price action. Haven't seen Surae and Sarang active of late? From the dev meeting logs that are forthcoming: <fluffypony> Surae is also going to be picking up MRL-6 in the summer |
|
|
|
Who else is eagerly awaiting the hard fork at block 1,009,827?
It sure is not minergate.com (and some other pools). Please move to a different pool because they still did not upgrade! Hopefully the miners (or botnet owner?) quickly realize that they do not receive any block rewards anymore and move shortly after to one of the many other available pools. But I for sure am looking forward, have the count down timer open all the time: http://myrcraft.com/xmr.htmlThey said on twitter today that they will upgrade tonight. See conversations with the official Monero account here: https://twitter.com/MinerGate/with_replies |
|
|
|
So, is there an official GUI wallet for XMR and if not, WHY THE HELL NOT?
Because the database was more important than the GUI. Standard GUI comment: |
|
|
|
Ariel I feel you're pain man, after losing like 13000 Monero's at monerodice making you like the biggest loser on the site you could've instead earned that selling now; I would cry in a corner just because of that alone. But u don't have to hate on people choices man be strong buddy we learn from our mistakes.
Ariel ≠ Arielbit. He already explained that a few times, don't be so ignorant. |
|
|
|
Monero v0.9.3 - Hydrogen Helix - released! (Urgent and important bug fixes to 0.9.2 Hydrogen Helix) https://github.com/monero-project/bitmonero/releases/tag/v0.9.3
Information from Github:This has urgent and important bug fixes to 0.9.2 Hydrogen Helix - Urgent bug fix for database corruption issues in 0.9.2
- Official Windows 32-bit releases are back
- Updates to miniupnpc
- Sets v3 fork date for September, 2016
- Fixes core tests and re-enables them
- Fixes a problem with --password-file not working in RPC mode
<snip> P.P.S. As long as you are on any 0.9.x version in advance of the hardfork you are fine. Clarification question: From a hard fork perspective, any version of 0.9.x will be compatible. However, from a stability perspective, any version 0.9.x, except 0.9.2, are acceptable since it seems that only 0.9.2 suffers from the database corruption issues, correct? Correct, preferably run 0.9.3 since it includes the most recent fixes over all Hydrogen Helix versions. |
|
|
|
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? yes all the coins were mined ,be send from the pools. all the dust are 1.73 ,i tried to send 100 xmr from my wallet fee is 2.1 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. |
|
|
|
Hi guys,new forum memer here!
I would like to ask if there is any lightweight monero wallet that keep my monero safe locally offline.
Thanks in advance!
Most safe strictly for cold storage is a paper wallet. Here is a guide: linkIf you want a lightweight GUI wallet you can occasionally use to transact, try this one: https://bitcointalk.org/index.php?topic=903579.0I think you could use it on a computer that is kept offline most of the time. How safe is it making a cold storage wallet with .simpleawallet and just keeping the key file safe offline compared to the procedure explained in the guide? Pretty much the same as long as it is all done offline, the keys are never brought online and you check the integrity of the simplewallet you are using. There is an older guilde for doing safe cold storage with simplewallet, but I don't have a link to it. Maybe someone will reply with the link. Found it: Hey everyone,
What security measures do you recommend for your cold storage keys. I was thinking more about measures to prevent hacking/theft of the keys. Should i be paranoid to the point of creating the wallet in an air gap and never look into it until I need it? (Lets not go into the "Ruiu says badBIOS leaps air gaps" territory).
Regarding backup I'm doing the _strongly encrypt your files and stored them in offline and online sources and don't forget the deterministic seed_ routine. If anyone as further thoughts on backup that would be appreciated also.
Remember, rockets are old school. We are going to the moon in a space elevator. Keep calm and get some moar.
Peace!
My suggestion is as follows: 1. Take any machine you have lying around, even your normal workstation. You may find it easier to use an older computer that has no wifi or bluetooth if you're particularly paranoid. 2. Create a Linux or Windows bootable disk, and make sure you have the Monero binaries on the same disk or on a second disk (for Linux make sure you have also downloaded copies of the dependencies you will need, libboost1.55 and miniupnpc for instance). 3. Disconnect the network and/or Internet cables from your machine, physically remove the wifi card or switch the wifi/bluetooth off on a laptop if possible. 4. Boot into your bootable OS, install the dependencies if necessary. 5. Copy the Monero binaries to to a RAM disk (/dev/shm in Linux, Windows bootable ISOs normally have a Z: drive or something) 6. Don't run the Monero daemon. Instead, using the command line, use simplewallet to create a new wallet. 7. When prompted for a name, give it any name, it doesn't really matter. 8. When prompted for a password, type in like 50 - 100 random characters. Don't worry that you don't know the password, just make it LONG. 9. Write down (on paper) your 24 word mnemonic seed. 10. Write down (on your phone, on paper, on another computer, wherever you want) your address and view key. 11. Switch off the computer, remove the battery if there is one, and leave it physically off for a few hours. There you go - the wallet you've created was created in RAM, and the digital files are now lost forever. If some magical hacker manages to somehow get the data, they will lack the long password to open it. If you need to receive payments, you have the address, and you have the view key if needed. If you need access to it, you have your 24 word seed, and you can now write out several copies of it so that you have an offsite copy (eg. a bank deposit box). Due to the nature of the key you can write it as part of something else - eg. write a fake love letter to your wife so that the 24 words on the left hand side are your key or whatever. Then write a bunch of extra love letters. That way, if your deposit box is ever discovered, it'll be disregarded as unimportant love letters. |
|
|
|
Hi guys,new forum memer here!
I would like to ask if there is any lightweight monero wallet that keep my monero safe locally offline.
Thanks in advance!
Most safe strictly for cold storage is a paper wallet. Here is a guide: linkIf you want a lightweight GUI wallet you can occasionally use to transact, try this one: https://bitcointalk.org/index.php?topic=903579.0I think you could use it on a computer that is kept offline most of the time. How safe is it making a cold storage wallet with .simpleawallet and just keeping the key file safe offline compared to the procedure explained in the guide? Pretty much the same as long as it is all done offline, the keys are never brought online and you check the integrity of the simplewallet you are using. There is an older guilde for doing safe cold storage with simplewallet, but I don't have a link to it. Maybe someone will reply with the link. This guide is based on that: https://www.reddit.com/r/Monero/comments/48cgmd/an_extensive_guide_for_securely_generating_an/I started with the cold wallet instructions provided by Fluffypony, but decided that using Moneromooo's offline wallet generator was easier and ultimately simpler to verify authenticity (and fluffypony agreed) |
|
|
|
|
Show Posts
