for all who maybe ask the same question I wanted to provide an answer to my question to my best knowledge.
What I basically described above is the concept of a "hot wallet". As, in the example above, the account is created directly at the node, all data, keys etc are stored on that node.
Now as wallets, or containers of keys, should not (and I guess, cannot) be copied across nodes, the initial question is actually pointless or plain wrong. Another problem is that I actually asked two questions in one.
Transferring something from account1.node1 to account1.node2 is no problem at all (within the same network). Simply do:
eth.sendTransaction({from:sender, to:receiver, value: amount})
The other question I was asking myself was kinda along the lines of a blockchain explorer. Listing, via web3, what's going on in the network.
With web3.js one can query all account data on any specified node, but not all accounts within a given private blockchain installation (unless someone tells me otherwise).
I hope that helps someone at some time :)
Borinho
I think it had previously been a part of the "Geth and Tools" release package, but it's gone missing... An issue was raised a couple of days ago: #3703
With regards to what it does, further up the page you linked to there's a description of each of the standalone tools (yes, they're separate executables):
bootnode
Stripped down version of our Ethereum client implementation
that only takes part in the network node discovery protocol, but does
not run any of the higher level application protocols. It can be used
as a lightweight bootstrap node to aid in finding peers in private
networks.
Best Answer
Using node hex in
nodekey
file under.ethereum/geth/nodekey
and bootnode utility.Assuming you are using Linux.
Check your nodekey hex :
Then with bootnode utility :