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

[Arux]

Sorry guys, too lazy to back read this humongous thread, but can someone post a pic of what the official GUI would look like?

https://i.imgur.com/FewKbG1.png

and :
https://www.evernote.com/l/AhBiaAEvDzhHd5p2l4Vg90Ff3PmnxzUCzPA
https://www.evernote.com/l/AhAvGRmGZzZC7I5-VBmaMMr9LazAAsP6VPE
https://www.evernote.com/l/AhDu23hm5y1B652JSUuWd5iip96kRHPJrGE
https://www.evernote.com/l/AhAFgFgjW0tJUpiTaJjw1-DvdSgkQ0n2w1o
https://www.evernote.com/l/AhCZGE9r-3hERpy1pvYVgMEj_yZ4pxQyE4I
https://www.evernote.com/l/AhD0SgwPv5ZN64VbkL3RNvq2b-Ikt4xtzfY
https://www.evernote.com/l/AhBrep2IOE1Fl6q0x0HD5DUsvQlRcQ9mKRk
https://www.evernote.com/l/AhBCfYAqKaBEHrzbK_owLA-CFvJA5wNgreE
https://www.evernote.com/l/AhB8sCz8qJpPWIq2_Wayss2fCy9Iq5SOLhA
https://www.evernote.com/l/AhCrtvSWmvdLQpSLkZb34pD3a1zEDSsMQAc
https://www.evernote.com/l/AhApVs-0GQZIzYcWA_Lb0Gfjzu8G1I7-kUU

from https://forum.getmonero.org/9/work-in-progress/2476/the-official-qt-gui-project

[1714661963]

1714661963

[1714661963]

1714661963

[1714661963]

1714661963

[1714661963]

1714661963

[1714661963]

1714661963

[5w00p]

IS it glue?

[luigi1111]

Need some help with simplewallet here:

I'm having an ongoing issue where outgoing XMR transfers do not make it into the next block, and sometimes not for several blocks.  This wreaks havoc with ShapeShift because they cancel the transaction if your deposit if it's not confirmed in a block within 10 minutes.

If Monero blocks are not nearly full like Bitcoin and miner fees are automatic, what else could it be?

Example:

Code:

[wallet]: transfer xxx........
Money successfully sent, transaction <xxx........>
[wallet]: bc_height
1085653
[wallet]: bc_height
1085654
[wallet]: bc_height
1085655
[wallet]: bc_height
1085656
Height 1085656, transaction <xxx........>, spent xxx........

Why didn't that xfer get included in block 1085654 or 1085655?  Thanks for the help!

I don't know how to answer the question but I had a tx in block 1085656, I wasn't paying much attention but I was surprised it took a few blocks to get confirmed. My only guess is with the rapid increase in activity and hashrate over the past couple days there seems to be a lot of variance at the moment...two blocks found within seconds then 10 minutes between blocks: http://moneroblocks.info/

Notice the tx per block is higher than average: http://moneroblocks.info/stats

I'm sorry to hear that Shapeshift is not recognizing the payment as soon as it hits the tx pool. Use xmr.to. I have communicated with a Shapeshift dev on how to get the payment id from the tx pool but I guess they are too busy or something...

Just checking the payment ID isn't a good practice. Pulling and scanning (viewkey/normal wallet stuff) the mempool is fine; that's what xmr.to does AFAIK.

[GingerAle]

Need some help with simplewallet here:

I'm having an ongoing issue where outgoing XMR transfers do not make it into the next block, and sometimes not for several blocks.  This wreaks havoc with ShapeShift because they cancel the transaction if your deposit if it's not confirmed in a block within 10 minutes.

If Monero blocks are not nearly full like Bitcoin and miner fees are automatic, what else could it be?

Example:

Code:

[wallet]: transfer xxx........
Money successfully sent, transaction <xxx........>
[wallet]: bc_height
1085653
[wallet]: bc_height
1085654
[wallet]: bc_height
1085655
[wallet]: bc_height
1085656
Height 1085656, transaction <xxx........>, spent xxx........

Why didn't that xfer get included in block 1085654 or 1085655?  Thanks for the help!

I don't know how to answer the question but I had a tx in block 1085656, I wasn't paying much attention but I was surprised it took a few blocks to get confirmed. My only guess is with the rapid increase in activity and hashrate over the past couple days there seems to be a lot of variance at the moment...two blocks found within seconds then 10 minutes between blocks: http://moneroblocks.info/

Notice the tx per block is higher than average: http://moneroblocks.info/stats

I'm sorry to hear that Shapeshift is not recognizing the payment as soon as it hits the tx pool. Use xmr.to. I have communicated with a Shapeshift dev on how to get the payment id from the tx pool but I guess they are too busy or something...

Just checking the payment ID isn't a good practice. Pulling and scanning (viewkey/normal wallet stuff) the mempool is fine; that's what xmr.to does AFAIK.

I've also heard rumor that delayed transaction entry into a block can be caused by a version problem between daemon and wallet. Some dude on IRC was getting this behavior because he was using a remote node. God knows what version the remote node is using - anything since 0.9.0 will be at consensus, but 0.9.0 -> 0.9.3 all had their fair share of bugs that were squashed. https://github.com/monero-project/bitmonero/releases

So, by any chance are you using a remote node?

If so, run the daemon! Run a node! Change the world!

[mmortal03]

I'm having an ongoing issue where outgoing XMR transfers do not make it into the next block, and sometimes not for several blocks.  This wreaks havoc with ShapeShift because they cancel the transaction if your deposit if it's not confirmed in a block within 10 minutes.

I assume you're experiencing this when using ShapeShift's precise option, correct? I've tried to avoid the precise option due to exactly what you describe, but have actualy experienced an issue this morning (CST) with their *quick* option, converting XMR to BTC, where the ShapeShift status page acted as if it never received the deposit. It still hasn't, five hours later, even though the transaction showed up on the Monero blockchain five hours ago. I've contacted ShapeShift's support with the TransactionID and PaymentID, of course, but I haven't heard back from them yet.

[toffoo]

I've also heard rumor that delayed transaction entry into a block can be caused by a version problem between daemon and wallet. Some dude on IRC was getting this behavior because he was using a remote node. God knows what version the remote node is using - anything since 0.9.0 will be at consensus, but 0.9.0 -> 0.9.3 all had their fair share of bugs that were squashed. https://github.com/monero-project/bitmonero/releases

So, by any chance are you using a remote node?

Both my bitmonerod and simplewallet are the latest 0.9.4.0 Hydrogen Helix and the daemon is running locally.

I assume you're experiencing this when using ShapeShift's precise option, correct? I've tried to avoid the precise option due to exactly what you describe, but have actualy experienced an issue this morning (CST) with their *quick* option, converting XMR to BTC, where the ShapeShift status page acted as if it never received the deposit. It still hasn't, five hours later, even though the transaction showed up on the Monero blockchain five hours ago. I've contacted ShapeShift's support with the TransactionID and PaymentID, of course, but I haven't heard back from them yet.

Trying several types of monero ShapeShift deposits over the past few weeks, I've only been about 25% successful getting my transfer in a block before they cancel in 10 minutes.  But if you give them the monero refund address they've refunded my deposit within 30-60mins, nearly all the time.

[mmortal03]

Trying several types of monero ShapeShift deposits over the past few weeks, I've only been about 25% successful getting my transfer in a block before they cancel in 10 minutes.  But if you give them the monero refund address they've refunded my deposit within 30-60mins, nearly all the time.

Yeah, unlike the precise option, my understanding is that you don't have the 10 minute time limit with the quick, but you just don't lock in your rate. I gave them a refund address when I did the quick, but if it doesn't even detect the deposit in the first place, which is what I'm experiencing, then I suspect that they aren't able to automatically give a refund. I have no idea why it wouldn't even see the deposit.

[mmortal03]

One other thing, has anyone noticed MyMonero stating a different payment and fee amount on the confirmation page than when you actually look up the Transaction ID? Once I get my other issue handled with ShapeShift, I'll post an example with the Transaction ID versus what MyMonero's output was.

[btcnoob85]

Do you think Monero price can quickly climb to the level of 0.015?

What is the basis of that assumption?

[luigi1111]

One other thing, has anyone noticed MyMonero stating a different payment and fee amount on the confirmation page than when you actually look up the Transaction ID? Once I get my other issue handled with ShapeShift, I'll post an example with the Transaction ID versus what MyMonero's output was.

Payment amount is probably due to change, which depends on what inputs are selected.

The fee shouldn't be different though; I'd be interested to see that.

[mmortal03]

One other thing, has anyone noticed MyMonero stating a different payment and fee amount on the confirmation page than when you actually look up the Transaction ID? Once I get my other issue handled with ShapeShift, I'll post an example with the Transaction ID versus what MyMonero's output was.

Payment amount is probably due to change, which depends on what inputs are selected.

The fee shouldn't be different though; I'd be interested to see that.

As soon as I get my refund from ShapeShift, I'll post the seemingly odd difference that I saw with the MyMonero transaction. I don't want to post it until I've worked everything out with ShapeShift, though. Btw, they said that they were, indeed, having issues with their Monero client that should now be fixed, but I don't know the details. I'm still waiting on them to initiate the refund.

[GingerAle]

http://nodebox.link/ , new ISO is up for download!

Features Monero nvidia mining software, CPU mining software, MiniNodo wallet server, Pool server, and Monero Core.

Just download it, put it on a USB stick, and install on an old computer, and now you got a node!

Also features amazing spinning status icons.

[mmortal03]

One other thing, has anyone noticed MyMonero stating a different payment and fee amount on the confirmation page than when you actually look up the Transaction ID? Once I get my other issue handled with ShapeShift, I'll post an example with the Transaction ID versus what MyMonero's output was.

Payment amount is probably due to change, which depends on what inputs are selected.

The fee shouldn't be different though; I'd be interested to see that.

OK, here you go. This was what MyMonero's confirmation page told me when I originally sent it. I simply copied and pasted the following from it into a text file, and only did this once, so there couldn't have been any mix-up on multiple transactions (the wallet only contained ~26.33 XMR):

Code:

Amount
26.23493623 (+0.06 fee)
Payment ID
68bf7209978fcc3ac1227c962e0be4cb55cd7873f234dae8eb50006ba7fe5759
Transaction ID
c969039420df1f884463b5c4a4ad0fc45d5756b40bdc9097a55aa6d0bc1c7cb7

However, if you look the transaction up on Chainradar, it shows:

Code:

26.274936230000 (+0.045063770000 fee)

See here: http://chainradar.com/xmr/transaction/c969039420df1f884463b5c4a4ad0fc45d5756b40bdc9097a55aa6d0bc1c7cb7

Could it be possible that I somehow accidentally double spent with two different transactions when trying to find an appropriate fee? I only had enough XMR to spend close to that total amount once (as I was trying to spend my entire wallet), but I kept getting "not enough spendable outputs", so I decreased the amount I was trying to send each time until it finally went through, giving me the above information on the confirmation page. I did have the wallet open in another window at one point, but I only recall getting the error messages there -- no confirmation page. I would have realized it if I'd gotten two confirmation pages during the course of this.

[LucyLovesCrypto]

One other thing, has anyone noticed MyMonero stating a different payment and fee amount on the confirmation page than when you actually look up the Transaction ID? Once I get my other issue handled with ShapeShift, I'll post an example with the Transaction ID versus what MyMonero's output was.

Payment amount is probably due to change, which depends on what inputs are selected.

The fee shouldn't be different though; I'd be interested to see that.

OK, here you go. This was what MyMonero's confirmation page told me when I originally sent it. I simply copied and pasted the following from it into a text file, and only did this once, so there couldn't have been any mix-up on multiple transactions (the wallet only contained ~26.33 XMR):

Code:

Amount
26.23493623 (+0.06 fee)
Payment ID
68bf7209978fcc3ac1227c962e0be4cb55cd7873f234dae8eb50006ba7fe5759
Transaction ID
c969039420df1f884463b5c4a4ad0fc45d5756b40bdc9097a55aa6d0bc1c7cb7

However, if you look the transaction up on Chainradar, it shows:

Code:

26.274936230000 (+0.045063770000 fee)

See here: http://chainradar.com/xmr/transaction/c969039420df1f884463b5c4a4ad0fc45d5756b40bdc9097a55aa6d0bc1c7cb7

Could it be possible that I somehow accidentally double spent with two different transactions when trying to find an appropriate fee? I only had enough XMR to spend close to that total amount once (as I was trying to spend my entire wallet), but I kept getting "not enough spendable outputs", so I decreased the amount I was trying to send each time until it finally went through, giving me the above information on the confirmation page. I did have the wallet open in another window at one point, but I only recall getting the error messages there -- no confirmation page. I would have realized it if I'd gotten two confirmation pages during the course of this.

Nothing is wrong. Mymonero attaches a small fee for each transaction:
https://mymonero.com/#/terms

5. Fees
5.1. Company Fees. Access to the account is free, but the Company may charge fees for additional Services. Specifically, and at a minimum, the Company can and does charge a fee for every transaction that is sent. Any applicable fees will be displayed in each Service.

[mmortal03]

Nothing is wrong. Mymonero attaches a small fee for each transaction:
https://mymonero.com/#/terms

5. Fees
5.1. Company Fees. Access to the account is free, but the Company may charge fees for additional Services. Specifically, and at a minimum, the Company can and does charge a fee for every transaction that is sent. Any applicable fees will be displayed in each Service.

That would make sense, the math just doesn't seem to add up to me. The amount+fee on chainradar in the transaction that was sent to ShapeShift adds up to 26.32, which is *larger* than the 26.29493623 amount+fee reported by MyMonero on the confirmation page. I'd think that it would be the other way around. Maybe someone can break down the math for me. It would also seem useful to have the confirmation page on MyMonero break it down into parts so that there's no confusion. Finally, is there a simple way to have MyMonero spend the contents of the entire wallet so that there's no need to manually figure out what amount to enter?

[GingerAle]

Nothing is wrong. Mymonero attaches a small fee for each transaction:
https://mymonero.com/#/terms

5. Fees
5.1. Company Fees. Access to the account is free, but the Company may charge fees for additional Services. Specifically, and at a minimum, the Company can and does charge a fee for every transaction that is sent. Any applicable fees will be displayed in each Service.

That would make sense, the math just doesn't seem to add up to me. The amount+fee on chainradar in the transaction that was sent to ShapeShift adds up to 26.32, which is *larger* than the 26.29493623 amount+fee reported by MyMonero on the confirmation page. I'd think that it would be the other way around. Maybe someone can break down the math for me. It would also seem useful to have the confirmation page on MyMonero break it down into parts so that there's no confusion. Finally, is there a simple way to have MyMonero spend the contents of the entire wallet so that there's no need to manually figure out what amount to enter?

I don't think so - that would require a sweep wallet kinda thing, or mix unspendable dust.

What you can do is take matters into your own hands and restore the wallet on your own computer. On MyMonero, get the viewkey and spendkey, and using simplewallet use the --generate-from-keys arg  starting flag, so simplewallet.exe --generate-from-keys arg for windows, or ./simplewallet --generate-from-keys arg for linux. Arg is the name of your new wallet. If you don't feel like running your own node, you can connect to a random remote node. So the total command would be

./simplewallet --generate-from-keys myrestoredwallet.bin --daemon-host node.moneroworld.com

Now, restoring remotely will take a while.

Once you get it restored, you can enter the command sweep_unmixable.

Actually, now that I think about it this really won't solve your issue. You may need to compile your own simplewallet to use the sweep_all . And all this will do is get your outputs into one output, which should then make figuring out the fee to empty your wallet really easy.

I have a hunch though that if you restore your wallet, the data will match whats on the blockchain.

[saddambitcoin]

One thing I have found with using Monero (simplewallet) on a regular basis, is that fees are highly variable due to the random input selection.

If you set "always confirm transfers" to 1 it will show you the fee before you approve the transaction, so I'll often try again if the fee seems very high, like 0.08 or something. Depending on the transaction amount it will usually go down to a reasonable 0.01-0.03.

I know it's just penny pinching Moneroj but who knows, maybe I'll be grateful in the long run for saving those Monero cents.

[mmortal03]

Finally, is there a simple way to have MyMonero spend the contents of the entire wallet so that there's no need to manually figure out what amount to enter?

I don't think so - that would require a sweep wallet kinda thing, or mix unspendable dust.

What you can do is take matters into your own hands and restore the wallet on your own computer. On MyMonero, get the viewkey and spendkey, and using simplewallet use the --generate-from-keys arg  starting flag, so simplewallet.exe --generate-from-keys arg for windows, or ./simplewallet --generate-from-keys arg for linux. Arg is the name of your new wallet. If you don't feel like running your own node, you can connect to a random remote node. So the total command would be

./simplewallet --generate-from-keys myrestoredwallet.bin --daemon-host node.moneroworld.com

Now, restoring remotely will take a while.

Once you get it restored, you can enter the command sweep_unmixable.

Actually, now that I think about it this really won't solve your issue. You may need to compile your own simplewallet to use the sweep_all . And all this will do is get your outputs into one output, which should then make figuring out the fee to empty your wallet really easy.

I have a hunch though that if you restore your wallet, the data will match whats on the blockchain.

Yeah, that makes sense from the perspective of reducing the wallet down to only what's spendable, but then you'd still have to calculate the right spend amount such that the total of spend + fee equals zero XMR remaining. saddambitcoin makes a good point about the "always confirm transfers" feature -- I was unaware of that. I will try it out.

[aminorex]

I know it's just penny pinching Moneroj but who knows, maybe I'll be grateful in the long run for saving those Monero cents.

At the very least, the excercise has increased your understanding of the systems behavioural surface.  And the policy of seeking such understanding is not  unlikely to save you from loss, if only lost opportunity, in unforseeable future circumstances.

[666z00m]

Hello! Can somebody explain me how hash target works on monero?

in cpu-miner.c see this
       memset(work->target, 0xff, sizeof(work->target));
       work->target[7] = rpc2_target;

i see this in scanhash
   cryptonight_hash_ctx(hash, pdata, persistentctx);
   if (unlikely(hash[7] < ptarget[7])) {

so we are only concerned for hash[7] and target[7] really.

the way I understand target is 0xffffffff/diff, so it should be 1 at current diff right?
what happens when diff is over 0xffffffff ? we also check hash[6] or what?

and it's not obvious where this hash appears in the blockhash (like if I browser an explorer). for satoshi it's obvious where this is.

and how does monero actually validate this. could someone point me to the code that does this in the daemon?

Thanks!