na that points to getmonero
Right, my mistake. Should be corrected to "compile yourself" then :-P
|
|
|
Crosspost: downloads section on getmonero seems to be down.
From IRC: <_Slack> <fluffypony> the mining testnet node is down <_Slack> <fluffypony> completely borked an upgrade <_Slack> <fluffypony> software upgrade, I mean <_Slack> <fluffypony> unrelated to MM <_Slack> <fluffypony> and that’s also killed the relays and my IRC bouncer <_Slack> <fluffypony> have to wait for helping hands at the DC to go fix.
That's why getmonero.org is down too currently.
|
|
|
downloads section on getmonero seems to be down.
From IRC: <_Slack> <fluffypony> the mining testnet node is down <_Slack> <fluffypony> completely borked an upgrade <_Slack> <fluffypony> software upgrade, I mean <_Slack> <fluffypony> unrelated to MM <_Slack> <fluffypony> and that’s also killed the relays and my IRC bouncer <_Slack> <fluffypony> have to wait for helping hands at the DC to go fix.
That's why getmonero.org is down too currently.
|
|
|
xmr.link openalias site and service definitively dead ?
Can't remember who ran that service but it is probably better to set up your own open alias on your own domain if you wish to use it. Imagine if a lot of people started using a service like that, all it takes is a successful hack to switch all the addresses and maybe they steal some XMR before it gets noticed. Thank you. Is there a simple guide to install this function on my own domain ? What wallets accept openalias address format ? Mymonero ? Lightwallet ? Other ? Thanks MyMonero and simplewallet do for certain. Not entirely sure about Lightwallet, but I expect so because it simply is a wrapper of simplewallet. Guide: https://monero.stackexchange.com/questions/1364/how-do-i-map-a-domain-to-a-monero-address-via-openalias-org/1365#1365
|
|
|
Reading it now. So that will add even more anonymity? If so that will be huge. Correct. It solves some edge cases of the current anonymity. I'd suggest to read this article too: http://weuse.cash/2016/01/09/tying-up-loose-ends-with-ringct/In addition, read the other MRL papers (in particular MRL-0001 and MRL-0004).
|
|
|
Crosspost: We're forking testnet for RingCT testing. Everyone is welcome to participate and try to break it.
v3 happens in a few hours (just a change on coinbase validation). v4 happens in a bit more than a day, and rct txes become allowed. v5 happens in 3 days, and rct txes become mandatory (save if you have old unmixable inputs)
Pull the latest master. You don't need to resync anything if you already have a testnet database.
fluffypony will make binaries in the next day or two if you can't.
|
|
|
Thanks for the help. I found the tx id's of the 3 transactions and indeed the first two can be found via http://moneroblocks.info/ and the last one cannot. When I run rescan_spent though and subsequently run show_transfers the transaction is still there though. BTW: I'm still 1149 blocks behind. Can that be a problem? Possibly your tx was invalid and got rejected by other daemons. Had you sent a tx from the same address, but using another machine, within those 1149 blocks ? If so, you probably unknowingly double spent. In any case, if you use a recent enough wallet, you should see that last tx as "pending" in show_transfers. If it indeed hasn't propagated to the network, you can "flush_txpool" in the daemon, and the wallet will soon notice it and switch it to "failed". There is a bug (fixed in the rct branch) which will need you to run "rescan_spent" after that in order to get the right balance. But first, wait for the chain to be synced. I send 2 transactions that succeeded and then a third that I'm asking about because it's not in the blockchain, within those 1149 blocks, but all from the same machine. I'm using version 9.4.0 and I indeed see all 3 transactions as pending. I will try the commands after it is done syncing. I'm glad the chance of my Monero actually being lost seems to be extremely low Synced and the other 2 transactions are finalized now and the faulty transaction is still pending. rescan_spent did not fix it so I'm now rescanning the entire blockchain (which is taking a while). Rescanning the entire blockchain fixed this. Thanks for the help dEBRUYNE and MoneroMooo. To avoid this in the future I shouldn't send transactions with an unsynced blockchain? You're welcome! Yes. It's generally advised to let your blockchain fully sync first.
|
|
|
|