-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Online level zero accounts api call fix #7
Open
protoniuman
wants to merge
1,568
commits into
QORT:master
Choose a base branch
from
Qortal:online-level-zero-accounts-api-call
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Online level zero accounts api call fix #7
protoniuman
wants to merge
1,568
commits into
QORT:master
from
Qortal:online-level-zero-accounts-api-call
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
…al IP address changes.
…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.
…ity to those with sync issues.
… key, to make it easier for users to open.
…ed any kind of circular broadcasting.
…ally an OR not an AND.
…ace to test if authentication works.
/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).
…und 600ms to reply.
…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.
… rather than the current time.
…tputs relating to this wallet.
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.
…re coming back around 9-10 seconds later.
… items to process.
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.