[XMR] Monero - A secure, private, untraceable cryptocurrency

[Nik4691]

Monero 0.9.4 released!!

https://getmonero.org/2016/04/02/monero-0.9.4-released.html

SUMMARY OF CHANGES

This has important bug fixes to 0.9.3 Hydrogen Helix

Fix remaining issues with coinbase transactions
Removed connectivity_tool
Switched to new Clang move diagnostics
Added a new --generate-from-json flag to simplewallet to allow wallet creation from a JSON file
Add a new and improved version of sweep_dust
Various bug fixes to handle failures such as map resize failures and bad simplewallet exit[/li][/list]

Thanks.
I always unzip only bitmonerod and simplewallet to keep things clean in the directory.
And what is this cn_deserialize anyway?

[1714222412]

1714222412

[1714222412]

1714222412

[jwinterm]

Today dnaleor wrote on the Monero reddit that Poloniex took Monero onboard already on the 19th of May 2014. That is only one month after Monero got launched @ 2014.04.18
(I would btw suggest to change the date format on the really nice Excel with XMR Charts to YYYYMMDD or DDMMYYYY. MMDDYYYY really is confusing when only using numbers).

So who or what motivated Poloniex to adopt Monero in such an early stage? Did they just recognize the potential? You would assume they are mostly interested in volume, which has been rather moderate for quite some time even after it could be traded on Polo. Does someone in the Monero community have close contacts with Poloniex?

Or was Poloniex just trying to compete with Cryptsy (now goxed) where basically any altcoin was traded? It actually took Cryptsy quite some time to implement Monero, likely because of really being technically different and since before the 0.9 version it was heavy on the RAM usage.

Just curious.

In the beginning, Monero was only traded on a cryptonote only exchange run by TheKoziTwo, I think it was called exchange.cryptonote.to or something. Despite being relatively obscure, this impromptu exchange did decent volume. Several months before the launch of Monero, Poloniex was hacked and lost a bunch of user funds; they were a relatively small time exchange and I think looking for a unique and defining feature to set themselves apart. Enter Monero. Poloniex picked up Monero and there were huge volumes traded as soon as it got onboard. Not long after Poloniex offered XMR trading pairs, and the rest, as they say, is history.

[meme magic]

afair cryptsy wouldnt even put it on the voting list for about a year, they seemed to want nothing to do with it. mintpal put it on the voting list months before that, bunch of people forked over like 10-20 btc in votes and it was added a couple weeks later. many exchanges had it before cryptsy, and i seriously doubt the delay in implementation was technically related. likely more socially related imo.

cryptsy did the same thing with nxt.

the whole heavy on ram usage really wouldnt inhibit commercially designed hardware, most of that was just people using consumer grade hardware so i really doubt that had anything to do with it either.

[CrowdWhale]

Long term channel:




Reversal at bottom of the channel with higher highs and higher lows:




500k around April 12th

[meme magic]

not bad, my personal hope is that its closer to the 18-25th so i can complete a swing started a few days ago.

cant remember the last time i made a really good trade decision thay didnt involve buy, bury and forget though so ive already accepted that im going to lose out on lots.

[aiwe]

Concerning sweep_dust errors, it can be due to tiny inputs for which there is no enough inputs to mixin with.

Trying to sweep_dust, daemon says: 

Code:

Tx <...> has too low mixin (0), and more than one mixable input with unmixable inputs.

For example, when I am trying to send some xmr that left on my hot wallet, most of which consists of dust gives me an error:

Code:

Error: not enough outputs for specified mixin_count = 4:
output amount = 0.003811120000, found outputs to mix = 1
output amount = 0.007507490000, found outputs to mix = 1
output amount = 0.007723640000, found outputs to mix = 1
output amount = 0.003594340000, found outputs to mix = 2
output amount = 0.003064900000, found outputs to mix = 1
........  and so on....

There is enough
278.475450179850 xmr including unlocked dust
   1.247663779850

I wonder why balance differs after two digits after comma where dust begins. I am not good at math

[edit]: I am OK with that unusable dust, just hope everything works correctly.

From IRC:

<moneromooo> I think the <1e-2 part should be the same, yes. Maybe I'm missing a case.
<moneromooo> The sweep_dust failure is likely because it's dust that's too small, that is it's less than amount needed to send itself.
<moneromooo> Nothing can be done about those, except wait to see if fees go down later.
<moneromooo> One *could* pair a large output with a tiny dust one, and send, but you'd lose the dust and more of the large output than the dust, so rather pointless.

Thank you for your time. I'll just leave it as it is. It's a 'hot wallet' anyway. I just wanted to try this command sweep_dust and found this error interesting.

OK, now after fork I decided to try again. Now it lets me 

Code:

 sweep_dust
Sweeping 1.256077939850 for a total fee of 0.060000000000.  Is this okay?  (Y/Yes/N/No)Y
Error: transaction <143fafd751ccc6f1530e608f5db7acc393590651deb559c2d965df976ecc6f71> was rejected by daemon with status: Failed

daemon says

Code:

2016-Mar-24 09:19:14.124499 [RPC1]Tx <143fafd751ccc6f1530e608f5db7acc393590651deb559c2d965df976ecc6f71> has too low mixin (0), and more than one mixable input with unmixable inputs
2016-Mar-24 09:19:14.127498 [RPC1]tx used wrong inputs, rejected
2016-Mar-24 09:19:14.128999 [RPC1]Transaction verification failed: <143fafd751ccc6f1530e608f5db7acc393590651deb559c2d965df976ecc6f71>
2016-Mar-24 09:19:14.130499 [RPC1][on_send_raw_tx]: Failed to process tx

I must have screwed up something Gonna live with dust forever.

OK, upgraded to 0.9.4 and managed to get rid of all dust in one of my old hot wallet:

Code:

Balance: 0.531154229850, unlocked balance: 0.531154229850
[wallet 4AiWeK]: sweep_unmixable
Sweeping 0.299509959850 for a total fee of 0.060000000000.  Is this okay?  (Y/Yes/N/No)Y
Money successfully sent, transaction: <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>

Code:

Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.005397810000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.002935140000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.009024460000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.007789970000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.007684660000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.008264040000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.009665350000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.005714300000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.009685820000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.002667030000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.003594340000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.001224010000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.005082780000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.007507490000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.006756420000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.004659400000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.003106460000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.001332320000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.001449250000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.003811120000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.009560550000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.004146089850
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.002069510000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.000213280000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.009228280000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.006245180000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.007455200000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.007627150000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.007723640000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.006968980000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.000279470000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.002074560000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.004257230000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.008872500000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.007165050000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.004618300000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.007095450000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.002615000000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.057786400000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.005139050000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.003064900000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.001927850000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.002227010000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.007512200000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.006918700000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.004425180000
Height 1016789, transaction <d63c0dd5a5c813ac675f10eca0f5d509d97b254d8a7c8827944e8ab65753695e>, spent 0.004941080000

Now it works!!!! Like a charm! 

[magico]

https://getmonero.org/2016/04/02/monero-0.9.4-released.html
0.9.4 release is invalid. It seems dlls is missing.

edit: bitmonerod works with dlls form 0.9.3. I'm afraid to use simplewallet

[aiwe]

https://getmonero.org/2016/04/02/monero-0.9.4-released.html
0.9.4 release is invalid. It seems dlls is missing.

edit: bitmonerod works with dlls form 0.9.3. I'm afraid to use simplewallet

I took dlls form 0.9.3. And it seems to be working

[magico]

https://getmonero.org/2016/04/02/monero-0.9.4-released.html
0.9.4 release is invalid. It seems dlls is missing.

edit: bitmonerod works with dlls form 0.9.3. I'm afraid to use simplewallet

I took dlls form 0.9.3. And it seems to be working

Is it safe to use "dll"s v0.9.3 with "exe"s v0.9.4?

[mmortal03]

Monero 0.9.4 released!!

https://getmonero.org/2016/04/02/monero-0.9.4-released.html

SUMMARY OF CHANGES

This has important bug fixes to 0.9.3 Hydrogen Helix

Fix remaining issues with coinbase transactions
Removed connectivity_tool
Switched to new Clang move diagnostics
Added a new --generate-from-json flag to simplewallet to allow wallet creation from a JSON file
Add a new and improved version of sweep_dust
Various bug fixes to handle failures such as map resize failures and bad simplewallet exit[/li][/list]

The zip archives of Windows x64 0.9.3, Windows x86 0.9.4, and Windows x64 0.9.4 on the GitHub Monero releases page are all missing the requisite dlls.

[hyc]

https://getmonero.org/2016/04/02/monero-0.9.4-released.html
0.9.4 release is invalid. It seems dlls is missing.

edit: bitmonerod works with dlls form 0.9.3. I'm afraid to use simplewallet

I took dlls form 0.9.3. And it seems to be working

Is it safe to use "dll"s v0.9.3 with "exe"s v0.9.4?

The same build system was used for 0.9.3 as 0.9.4 so yes, the same DLLs should work fine.

[hyc]

Monero 0.9.4 released!!

https://getmonero.org/2016/04/02/monero-0.9.4-released.html

SUMMARY OF CHANGES

This has important bug fixes to 0.9.3 Hydrogen Helix

Fix remaining issues with coinbase transactions
Removed connectivity_tool
Switched to new Clang move diagnostics
Added a new --generate-from-json flag to simplewallet to allow wallet creation from a JSON file
Add a new and improved version of sweep_dust
Various bug fixes to handle failures such as map resize failures and bad simplewallet exit[/li][/list]

The zip archives of Windows x64 0.9.3, Windows x86 0.9.4, and Windows x64 0.9.4 on the GitHub Monero releases page are all missing the requisite dlls.

Windows x86 no longer needs any extra DLLs

[aiwe]

I removed previously copied from 0.0.3 dlls and without them simplewallet doesn't work, it sais:

Code:

The program can't start because libwinpthread-1.dll is missing from your computer. Try reinstalling the program to fix this problem.

So I put them back.

Ah, and I have monero.win.x64.v0-9-4-0

[MoneroMooo]

hyc specifically said x86, as in 32 bit arch, not x86_64. From reading the IRC, the 64 bit ones still need those libs, as you found out. This may soon be done with as well, but for not yet now.

[saddambitcoin]

Today dnaleor wrote on the Monero reddit that Poloniex took Monero onboard already on the 19th of May 2014. That is only one month after Monero got launched @ 2014.04.18
(I would btw suggest to change the date format on the really nice Excel with XMR Charts to YYYYMMDD or DDMMYYYY. MMDDYYYY really is confusing when only using numbers).

So who or what motivated Poloniex to adopt Monero in such an early stage? Did they just recognize the potential? You would assume they are mostly interested in volume, which has been rather moderate for quite some time even after it could be traded on Polo. Does someone in the Monero community have close contacts with Poloniex?

Or was Poloniex just trying to compete with Cryptsy (now goxed) where basically any altcoin was traded? It actually took Cryptsy quite some time to implement Monero, likely because of really being technically different and since before the 0.9 version it was heavy on the RAM usage.

Just curious.

They were just adding many many coins, plenty of stupid ones that I recall like the YIN/YANG coins. Not to mention they had been hacked in March of 2014 for 12% of their BTC. Monero turned out to be their first big hit and for most of 2014 it was the top volume coin there. The total exchange volume in BTC was nowhere near what it is now, but the success of Monero helped Poloniex to repay its customers for the losses incurred by the hack.

In June 2014 I think there were some 1000 BTC volume days for XMR (MRO at the time), this is known as the "Mintpal pump" as the XMR price went to 0.01 BTC after Mintpal announced they would be adding Monero. Of course, the price tanked when they did add the coin and Mintpal turned out to be a scam exchange anyway.

[binaryFate]

Today dnaleor wrote on the Monero reddit that Poloniex took Monero onboard already on the 19th of May 2014. That is only one month after Monero got launched @ 2014.04.18
(I would btw suggest to change the date format on the really nice Excel with XMR Charts to YYYYMMDD or DDMMYYYY. MMDDYYYY really is confusing when only using numbers).

So who or what motivated Poloniex to adopt Monero in such an early stage? Did they just recognize the potential? You would assume they are mostly interested in volume, which has been rather moderate for quite some time even after it could be traded on Polo. Does someone in the Monero community have close contacts with Poloniex?

Or was Poloniex just trying to compete with Cryptsy (now goxed) where basically any altcoin was traded? It actually took Cryptsy quite some time to implement Monero, likely because of really being technically different and since before the 0.9 version it was heavy on the RAM usage.

Just curious.

They were just adding many many coins, plenty of stupid ones that I recall like the YIN/YANG coins. Not to mention they had been hacked in March of 2014 for 12% of their BTC. Monero turned out to be their first big hit and for most of 2014 it was the top volume coin there. The volume in BTC was nowhere near what it is now, but the success of Monero helped Poloniex to repay its customers for the losses incurred by the hack.

This fact lead to one of the only two mentions of Monero on coindesk: http://www.coindesk.com/poloniex-claims-customers-repaid-following-march-bitcoin-hack/

If any coin should be singled out for helping to provide the boost in volume that enabled us to pay back customers quickly, it is Monero (XMR).

[nopedope89]

Hey guys, look, you can exchange 150 XMR for 5 cars on Changelly))



Looks like sexy girfriend is more difficult to get   Life, right?

[aiwe]

hyc specifically said x86, as in 32 bit arch, not x86_64. From reading the IRC, the 64 bit ones still need those libs, as you found out. This may soon be done with as well, but for not yet now.

Thanks for explanation, I think that then those dlls should be included in x64 archive, obviously they merely forgotten by mistake.

[nioc]

Ignorant DarkFlarber raises hand.  Can I upgrade from 0.9.3 to 0.9.4 binaries with no issues on windows 64?

[owlcatz]

Ignorant DarkFlarber raises hand.  Can I upgrade from 0.9.3 to 0.9.4 binaries with no issues on windows 64?

I just did, and it seems to be working fine, however i'm not fully synced yet (3 days, which is about the last time I ran it).