Skip to content

Online level zero accounts api call fix#7

Open
protoniuman wants to merge 1568 commits intoQORT:masterfrom
Qortal:online-level-zero-accounts-api-call
Open

Online level zero accounts api call fix#7
protoniuman wants to merge 1568 commits intoQORT:masterfrom
Qortal:online-level-zero-accounts-api-call

Conversation

@protoniuman
Copy link

No description provided.

CalDescent added 30 commits January 2, 2022 16:11
This can ultimately be replaced with a website list / search engine.
This allows an entire registered name to be preauthorized, therefore allowing for instance a website to automatically request other resources from the same author, such as videos.
This involves modifying the log4j2.properties file on node startup to fix an incompatibility with ${dirname:-}. Thanks to AlphaX Projects for tracking down this incompatibility.
… external IP changes to be detected without using a centralized service.
…efault port, match the peer's host with any entries in knownPeers and try connecting to each of those until one succeeds.
… signature combination.

This can help to inform decisions on data retention (although there is no deletion yet).
Even though a final decision is yet to be made, it makes sense to test with this scenario to ensure that everything works correctly.
This is likely longer than needed, but it's best to allow extra for now and then optimize the timeouts once we've had some experience with real world data.
1) Each relay request expires after 5 seconds, after which nodes will stop relaying it, preventing any kind of infinite loop. So it has to reach the destination peer within 5 seconds. This should be fine, because the original peer's request would timeout anyway, so there's nothing to be gained by continuing to relay it.

2) Each relay request stops being forwarded after 3 "hops" - i.e. once it has been relayed through 3 different peers, it will no longer be transmitted any further. If we assume that each node has 16 connections, that allows it to reach a theoretical maximum of 4096 peers in 3 hops. In practice it will be less, and may not reach everyone due to peer "islands". But it will automatically retry a few times on a timer, so should hopefully find what it needs eventually. Plus, it still has the ability to make a direct connection to anyone hosting the data, as long as they are port forwarded.
…lay mode is enabled in the settings or not.
… key, to make it easier for users to open.
CalDescent and others added 30 commits February 11, 2022 14:35
/render APIs use priority 10, whereas /arbitrary use priority 0, to prevent thumbnail downloads from holding up website loading. The priorities can be adjusted later, with maybe some service types being given higher priority than others.
…re than 1000ms on average to respond (measured over the last 5 requests).
…RT (average value based on community vote).
…fee. At some point we should determine the correct fee inside of generateBase(), but setting it explicitly adds confidence in testing for now.
This is the equivalent of increasing the max address gap from 15 to 21. The electrum standalone wallet uses 20, so this should be the most we will ever need.
… of network traffic, and are in the process of being replaced with a better method.
Added online zero level accounts to the response of /addresses/online/levels api endpoints
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants