No problem - I have to say thanks to you for this nice project. If I can help just let me know. :)

Addition: After one node has been shut down and im running into the problems it is also not possible anymore to join the network with new nodes through the bootstrap node. The new node tries to connect but is not possible to get key/value pairs (even if multiple other nodes are still online).

Okay maybe i just wrote it a little bit clumsy because my english is not the best one. Yes i know that all nodes have the capability to store and request key/value-pairs. I tried to make it as basic and as close as on your example files as possible. But after i made the Gist I now see that it was way to complicated (sorry)!

1. With "network collapses" i mean, that even when im just closing 1 node and still have a lot more nodes running (like 49 more nodes for example), not only the node turned off is getting kicked from all other nodes routing table, but also all the other nodes which where in the the routing table (and are still online) are getting kicked out of all other nodes (except of the bootstrap node). The result is, that after closing 1 of like 50 nodes the routing table of all nodes is breaking down in a way that i could not set or get other key/value pairs because the nodes are losing all neighboors and can't find any neighboors to make lookups for key/value-pairs.
2. I try to build a structure where i can have one node which is giving commands by setting key/value-pairs and all other nodes are periodically checking the key/value-pairs and taking action on the results and saving their results as key/value-pairs after that. I'm expecting that i can add new nodes and close them again and change the key/value pairs without the experienced behavior, that all nodes are losing their neighboors and can't get or set key/value pairs anymore.
3. I made a Gist with better instruction and comments in the comment section: https://gist.github.com/FlorianG2021/f03b429d06e652d5804c8ea5a55e2d39

Let me know if you need better information. Thanks for your help and this awesome project!

When i use multiple nodes like 1 Bootstrap with 1-x Nodes and 1-2 get/set Nodes the network collapses as soon as I close one of the Nodes. All nodes have different ports where they are listening on and getting bootstraped by the Bootstrap Node.

For an example I do this steps:

1. start the Bootstrap Node
2. start Node 1 and Node 2
3. start Setter Node 1 <- seems to break here (when setter node finished)
4. start Node 3
5. start Getter Node 1
6. close Node 2
7. start Node 4
8. start Node 5
9. start Node 6
10. start Setter Node 2
11. start Getter Node 2
12. start Node 7

Issue_Files+Logs.zip

I have the same results when i keep the Getter 1 and Setter 1 running in a while-true loop with "asyncio.sleep(5)". Than its crashing as soon as I close Node 2 and Start Node 4 (see step 6 and 7).

I tried many other combinations with less or more nodes and the result is always the same. The network always is collapsing with messages like this until setting and getting of key/value pairs is impossible and/or only the bootstrap node is left in the routing table:

Did not receive reply for msg id b'9vnyGd7GSadJyjd0ZHQRlMZ7g2w=' within 5 seconds
2021-06-23 11:20:09,156 - kademlia.protocol - WARNING - no response from 127.0.0.1:8472, removing from router

Normall the network should work normally when a node is getting closed right?

I am using "PyCharm Community Edition 2020.2.3 x64" on Windows 10 and Python 3.9.

Currently, we try to fetch profile and accreditation info even if those scopes aren't requested. This PR checks the configured scopes before hitting each API to ensure we don't bail out early because of a 403.

Additionally, this PR adds support for user_profile, which will soon be returned in /api/v1/me.