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

[bitebits]

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).

The Daemon runs fine under Windows X64, it is the wallet that is not functioning atm without the dll's.

[Drhiggins]

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.

dlls should be added to the zip file for 0.9.4.0 so that those installing bitmonerod for the first time don't get discouraged, especially Windows non command line users. 

[primer-]

Using latest binaries, 0.9.4 , still unable to access 89 xmr!

Starting refresh...
Refresh done, blocks received: 1
Balance: 117.345214014341, unlocked balance: 89.687114014341

transfer 2 44pFi8kPVuyeuGMYSUctVB1RMHyf6W8W7SNYTcmRWCrGcCTeA2xv68qiXUAvfuP3dNTnDuHFj8x8viY gzjo9cDZm7bysCV3 10
Error: not enough money to transfer, available only 0.000000000000, transaction
amount 10.000000000000 = 10.000000000000 + 0.000000000000 (fee)


transfer 2 44pFi8kPVuyeuGMYSUctVB1RMHyf6W8W7SNYTcmRWCrGcCTeA2xv68qiXUAvfuP3dNTnDuHFj8x8viY gzjo9cDZm7bysCV3 2
Error: not enough money to transfer, available only 0.000000000000, transaction
amount 2.000000000000 = 2.000000000000 + 0.000000000000 (fee)

[nioc]

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).

The Daemon runs fine under Windows X64, it is the wallet that is not functioning atm without the dll's.

Thanks.  As I want to do some wallet stuff I will wait till 0.9.4 is complete before upgrading.

[MoneroMooo]

Will be soon, fluffypony is rebuilding the missing libs I think.

[nioc]

Will be soon, fluffypony is rebuilding the missing libs I think.

Thanks   No rush on my end.

[aiwe]

Using latest binaries, 0.9.4 , still unable to access 89 xmr!

Starting refresh...
Refresh done, blocks received: 1
Balance: 117.345214014341, unlocked balance: 89.687114014341

transfer 2 44pFi8kPVuyeuGMYSUctVB1RMHyf6W8W7SNYTcmRWCrGcCTeA2xv68qiXUAvfuP3dNTnDuHFj8x8viY gzjo9cDZm7bysCV3 10
Error: not enough money to transfer, available only 0.000000000000, transaction
amount 10.000000000000 = 10.000000000000 + 0.000000000000 (fee)


transfer 2 44pFi8kPVuyeuGMYSUctVB1RMHyf6W8W7SNYTcmRWCrGcCTeA2xv68qiXUAvfuP3dNTnDuHFj8x8viY gzjo9cDZm7bysCV3 2
Error: not enough money to transfer, available only 0.000000000000, transaction
amount 2.000000000000 = 2.000000000000 + 0.000000000000 (fee)

Did you try to restore wallet from seed and rescan_bc from scratch?

[primer-]

Using latest binaries, 0.9.4 , still unable to access 89 xmr!

Starting refresh...
Refresh done, blocks received: 1
Balance: 117.345214014341, unlocked balance: 89.687114014341

transfer 2 44pFi8kPVuyeuGMYSUctVB1RMHyf6W8W7SNYTcmRWCrGcCTeA2xv68qiXUAvfuP3dNTnDuHFj8x8viY gzjo9cDZm7bysCV3 10
Error: not enough money to transfer, available only 0.000000000000, transaction
amount 10.000000000000 = 10.000000000000 + 0.000000000000 (fee)


transfer 2 44pFi8kPVuyeuGMYSUctVB1RMHyf6W8W7SNYTcmRWCrGcCTeA2xv68qiXUAvfuP3dNTnDuHFj8x8viY gzjo9cDZm7bysCV3 2
Error: not enough money to transfer, available only 0.000000000000, transaction
amount 2.000000000000 = 2.000000000000 + 0.000000000000 (fee)

Did you try to restore wallet from seed and rescan_bc from scratch?

Yes and it did not help. transfer_new did. Old transfer command is obviously deprecated and should be removed...
Amateur developers.. Shitcoin..

[wpalczynski]

Using latest binaries, 0.9.4 , still unable to access 89 xmr!

Starting refresh...
Refresh done, blocks received: 1
Balance: 117.345214014341, unlocked balance: 89.687114014341

transfer 2 44pFi8kPVuyeuGMYSUctVB1RMHyf6W8W7SNYTcmRWCrGcCTeA2xv68qiXUAvfuP3dNTnDuHFj8x8viY gzjo9cDZm7bysCV3 10
Error: not enough money to transfer, available only 0.000000000000, transaction
amount 10.000000000000 = 10.000000000000 + 0.000000000000 (fee)


transfer 2 44pFi8kPVuyeuGMYSUctVB1RMHyf6W8W7SNYTcmRWCrGcCTeA2xv68qiXUAvfuP3dNTnDuHFj8x8viY gzjo9cDZm7bysCV3 2
Error: not enough money to transfer, available only 0.000000000000, transaction
amount 2.000000000000 = 2.000000000000 + 0.000000000000 (fee)

Did you try to restore wallet from seed and rescan_bc from scratch?

Yes and it did not help. transfer_new did. Old transfer command is obviously deprecated and should be removed...
Amateur developers.. Shitcoin..

The 89 XMR is simply asshole tax you are being charged by the network.

[primer-]

The 89 XMR is simply asshole tax you are being charged by the network.

I can't wait for exchanges to run into this issue/bug...

[boestin]

Say primer, why dont you pm me your seed. I'll try to fix it over here, it could be a location issue

[saddambitcoin]

I've got a better idea. Don't accumulate dust! I suppose if you got it when the pools were paying out low amounts, that's not your fault. But any other reason now, it doesn't make sense to me. It's like going to the store and trying to pay them $200 in all pennies, then getting mad when they refuse to count it.

[aiwe]

For example Shapeshift is also sending dust. But I understand that. Next time will try to calculate deposit to receive rounded sum of monero in exchange.

[aiwe]

Moreover, it's like to suggest  to use only full Bitcoin not, say, 0.00370 BTC   What if tomorrow 1 XMR = 400$? I am glad that issues with "small" amounts being resolved.

[wpalczynski]

Moreover, it's like to suggest  to use only full Bitcoin not, say, 0.00370 BTC   What if tomorrow 1 XMR = 400$? I am glad that issues with "small" amounts being resolved.

Not at all.  Its about having similar amounts to mix with.  If the standard was fractional amounts being sent then there would be plenty of fractional amounts to mix with.

[GingerAle]

Moreover, it's like to suggest  to use only full Bitcoin not, say, 0.00370 BTC   What if tomorrow 1 XMR = 400$? I am glad that issues with "small" amounts being resolved.

Not at all.  Its about having similar amounts to mix with.  If the standard was fractional amounts being sent then there would be plenty of fractional amounts to mix with.

and i think ring ct takes care of all this

[saddambitcoin]

For example Shapeshift is also sending dust. But I understand that. Next time will try to calculate deposit to receive rounded sum of monero in exchange.

Sorry, I don't mean eliminate dust entirely, because that's impossible. My sentiment was directed towards people that have huge amounts of dust (like 89 XMR worth), from tons of tiny outputs. That didn't come from just withdrawing from an exchange. It's normal to have small amounts of dust and that can easily be resolved.

[aiwe]

I understand, I only suppose when those today's 'tiny' amounts tomorrow when monero hit 400$ will be usable  I got rid of dust and learned my lesson - collect monero in bigger chunks if possible, and round ones. The problem is that I also often collect small amounts. Not 89 xmr but still. Ah, and now simplewallet doesn't show unlocked dust at all, so it won't irritate people Most of users won't even know they got some dust anymore.

[Hueristic]

Hey, here's an idea Dumbass. TRY the FUCKING IRC DEV Channel!

Please, don't give that guy that idea (with anyone else, sure though).

LOL just -v if (i mean when) he trolls. It'll be Fun!

The 89 XMR is simply asshole tax you are being charged by the network.

ROTFLMFAO!

Seriously someone help him unload the rest so he's nowhere to be seen anymore.

Primer, why don't you just donate that wallet for a bug fix.

[americanpegasus]

Should people be accumulating 100 xmr worth of dust?  Probably not. 
 
Should the software/network be able to accomodate it?  Absolutely.   
 
We should be thankful to whoever pointed out this glitch.