I don't understand what you are asking.
Edit: unrelated, but I think just putting a hash of whatever you want to prove as a payment ID of any random transaction is far better than generating a private key with it.
I'm going to start this thread as a precursor for additions to the official website section.
These tools can be used to gain information about the Monero network or your transaction data in the blockchain.
Submit hash of file to blockchain. Could be used similar to blocksign or proof of existence if anyone hosts it
https://github.com/ShenNoether/MiniNero/blob/master/MoneroProof.py
PHP Payment thing
https://bitcointalk.org/index.php?topic=583449.msg11108919#msg11108919
Some question for the devs: What hash functions does Monero use for computing tx ids and key images?
The txids use keccak. The key images computed by hashing the tx public key using keccak to get a curve point*, then multiplying by the private key.
Thanks! You are referring to plain Keccak and not CryptoNight, right?
Yes cn_fast_hash which calls keccak1600. CryptoNight is cn_slow_hash
Thanks. BTW, hash length seems to be 256 bits for both.
need to add this to the check your transaction was recieved thing:
For this to work, you'll first need to run in simplewallet the command
set store-tx-keys 1
After that, you'll be able to get the private key of individual transactions by running the command
get_tx_key
from osensei on reddit. Would also be awesome if in general that code was put into simplewallet.
luigii, have you hosted that code anywhere else?
Nope, that's not the case. I operate monerohash.com. I'm getting the entire peer list from the daemon (not just the ones that the daemon is connected to) and making a connection attempt to each one of them every hour, if it works, then it's added to the map and to the count.
The daemon returns two lists of peers, the white and the gray. I'm not sure what's the concept behind their names, as they have even been switched on this commit from May 28th. But the case is that the gray list seems to show the most recent and working nodes (hence I would call it "white"), and the other one seems to accumulate all the other peers that have ever been seen.
Right now the node I'm using for this (which is pretty up to date with master, and is not the one I'm using for the pool - that one is on latest stable release) has 788 peers in the gray list and 4996 on the white. From those on the white list there are only 2 or 3 that may be accepting connections on the port specified, but I'm not checking that list because to me it seemed like a waste of work to make ~5k connection attempts every hour to only get 2 or 3 working, which I'm not even sure they are monero nodes, as that list goes back as peers seen for the last time 390 days ago. So I'm checking only the peers on the gray list.
make sure you have a clear path to the internet. For a while I thought I did because I had port forwarding set up on my router, but it turned out my cable modem ALSO had a firewall.
Also, I don't know how often monerohash updates their stats, so 10 hours might not be enough. And furthermore, both the i2p and the monerohash seem to only list nodes with > 70% uptime
I have 2 full nodes running, without miner, and they do not show up in the map. That's why I concluded this. On the other hand, they might use bitmonerod to obtain this list and I'm not sure if the peer list in this app contains all nodes of the network.
@luigi1111 I'm not exactly a css wizard but I will give it a try in spiffying it up a bit.
If anything is funky/not working as expected with those pages, please let me know. You can also save the webpage and use it offline (or at least locally in case the online version got compromised).
Edit: when I posted this only my pages were up (llcoins.net). I am not affiliated with the other pages.