Ask a node for it's peer list, sorted on `last_seen`:
`python3 peer_retreiver.py 212.83.175.67 18080`
`python3 peer_retreiver.py 145.239.93.75 34567`
```python
>> created packet 'handshake'
>> sent packet 'handshake'
<<receivedpacket'support_flags'
<<parsedpacket'support_flags'
<<receivedpacket'handshake'
<<parsedpacket'handshake'
99.48.XX.XX:18080
62.24.XX.XX:18080
93.44.XX.XX:18080
238.137.XX.XX:18080
163.86.XX.XX:18080
250.227.XX.XX:18080
99.48.XX.XX:34567
62.24.XX.XX:34567
93.44.XX.XX:34567
238.137.XX.XX:34567
163.86.XX.XX:34567
250.227.XX.XX:34567
[...]
```
@ -38,10 +31,10 @@ A Levin header (33 bytes) looks like this:
5. `u_int32` - Protocol version. Usually `01`
The payload that comes after that is a serialized Boost struct, which can be found
in the Monero codebase, e.g: [cryptonote_protocol_defs.h](https://github.com/monero-project/monero/blob/58ce16d4d91518b674a5d46419809f56f71d9114/src/cryptonote_protocol/cryptonote_protocol_defs.h).
in the Wownero codebase, e.g: `cryptonote_protocol_defs.h`.
The terminology for a (possible nested collection) of structs is called a `Section()` in this module.
For the actual serialization from the perspective of Monero, check out [portable_storage_to_bin.h](https://github.com/monero-project/monero/blob/58ce16d4d91518b674a5d46419809f56f71d9114/contrib/epee/include/storages/portable_storage_to_bin.h)
For the actual serialization from the perspective of Wownero, check out `portable_storage_to_bin.h`.
For deserialization look at `Reader.read_storage_entry()` and `Reader.read()`.
@ -61,4 +54,4 @@ Lastly, this module is presented as 'best effort' and, for example, does not gua