Hot answers tagged

18

There is a default set of nodes in the monero source code that it will attempt to use. These default nodes are used to bootstrap the list of peers your node will connect to initially. Nodes are able to request a list of peers from the other nodes they are connected to, which produces a large set pretty quickly. This is helpful to let you get a node up and ...


14

Kasisto is a web app enabling you to receive person to person Monero payments in small cafes, bars or shops. It will accept unconfirmed payments which makes it pretty much instant, but also means you should only accept smaller amounts since there's always a chance of a transaction not getting mined. I'm the developer, the source is on GitHub: amiuhle/...


12

You can put potentially any data into tx_extra and it will be stored on the blockchain with your transaction, only accessible with your keys. This however, will bloat your transaction size and your transaction will be more expensive as you have to pay per kb. For now, beside the elastic blocksize limit (median of last 100 blocks * 2) there is no maximum how ...


12

There will be three modes: I2P only: all traffic goes through I2P Clearnet only: all traffic goes through clearnet I2P/clearnet bridged: blocks go through clearnet, transactions go through I2P Since everyone will not be able to use I2P, it will be necessary that some nodes run in mixed mode to avoid the network partitioning. Since the blocks aren't secret, ...


9

It's a two way connection, the IN refers to connections initiated by the peer, and OUT refers to connections initiated by your node, but communication is duplex. In that status command, the X+Y part is X OUT connections and Y in connections. You're connected to all of these nodes, the only difference is which side initiated the connection.


8

It would not bring the monero network down. At most, it would prevent new nodes from adding to the network. The seed nodes are "well known" nodes which act as the first port of call for newly setup nodes. Once a node is already in the network, it does not need the seed nodes. If a node stops and is then restarted after a delay, the list of known peers is ...


7

Yes. I think exchanges and such will probably want to remain on clear net. This will require some nodes to operate as "bridge" nodes that will route information between clear and i2p networks.


6

It would be technically possible. However, several considerations apply: how do you trust what you receive is really a bona fide update ? You trust the blockchain because it's got PoW with high enough difficulty, but transactions are arbitrary. There is no mechanism to authentify the origin of something on the Monero P2P network. you don't want to put this ...


6

I did find the following information: Some information about the history you can find here. It is part of the so called 'epee' library. The creator is a Russian programmer called Andrey N. Sabelnikov, who seems to be well known for creating a botnet. The original code is located on Github. It doesn't seem to be used anywhere else besides some ...


6

The explorer is likely listing the transasctions that are in the pool (ie, not yet mined). Recent simplewallet will show those with show_tranfers, as "pool". Bear in mind that a transaction in the pool which hasn't been mined is not yours yet. If all goes well, it'll be yours soon, but you should not trust a pool transaction yet for large amounts if you ...


5

Nodes are aware of the nodes that they are connected to and can request a list of peers from those nodes. These lists can identify a many nodes, but a significant number will always be missed. Some nodes are only online part time, may have closed ports, or frequently change IP addresses, making accurate tracking more difficult. Monero Hash attempts to track ...


5

The basics are already here: encrypted payment IDs are private information encrypted by the sender, which only the recipient can decrypt. If the sender and the recipient are the same party, you can store data that only yourself is able to recover. A similar system could be used to enable "chat like" behavior. Transactions would have to be marked as non-...


4

Pretty sure that's how it works. You can also use the command "status" and you'll see at the end of the line a number like "8+1" this shows the number of nodes you are connected to, and after the + shows the number of nodes you are serving.


4

would it be possible to distribute updates by using the existing Monero P2P network of full nodes? Yes, it is possible. It would require some sort of built-in torrent-like code. If this is technically possible, is there also a way the mining network could also verify the authenticity of the download? Yes, the hash of the file could be stored in a block ...


3

Yes. In theory, binary data of the file could be encoded in one or multiple transactions, and stored in TXextra. If the community trusted the owner of the wallet creating those transactions, then it could be a way to do what you described. However, I don't see any benefit in doing so, as it only adds redundancy and no additional security compared to signing ...


3

Not sure random debug log questions are on topic for stack exchange, but... Field 2 is the thread logging this message. Hop is the (untrusted) number of peers forwarding the object. COMMAND_TIMED_SYNC is one of the P2P traffic messages.


3

While opening ports does put you more at risk than having none open, you are only in danger if an attack can exploit the service that is using that port. An open port is not an all access pass to your PC/network if an attacker happens upon it. They would need to manipulate whatever it is on the other side to gain some type of basic system access. Then they ...


2

There are some resources I know about for tracking this information. As Smart Kid already mentioned, these are not complete lists, though they may give you a good idea. The MoneroBase Geomap The MoneroHash Active Nodes Distribution XMR.BE This website lists all the Monero nodes with RPC open.


2

If uPNP won't cooperate, you can create a port forwarding rule (in Firewall > NAT > Port Forward) for the WAN interface that directs a destination of port 18080 to port 18080 of the internal IP of your node. This will have the effect of also creating a firewall rule on the WAN interface that allows the traffic arriving at port 18080 to pass through to the ...


2

Daemons (nodes) talk to each other using the epee levin protocol. https://github.com/monero-project/monero/tree/master/contrib/epee/include/net https://github.com/monero-project/monero/blob/master/src/p2p/net_node.h Both the wallet and daemon also expose JSON-RPC servers (so JSON sent over HTTP). The methods are documented at: https://getmonero.org/...


1

Monero uses the Levin protocol for p2p comms. Similar question here. The definitions for the commands are here.


1

This file contains the list of peers the node knows about, along with the time they were last seen. Deleting it clears that memory, and the node will have to rely on seed nodes to get a new list of peers. Keeping this file means that you don't have to rely on the seed nodes to be able to connect to the Monero network, as you already know of a large number ...


Only top voted, non community-wiki answers of a minimum length are eligible