-
Notifications
You must be signed in to change notification settings - Fork 145
Add Subspace to the list #110
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
Open
EmilFattakhov
wants to merge
1
commit into
polkadot-developers:master
Choose a base branch
from
EmilFattakhov:patch-1
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
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's certainly not the first. This trilemma was always bullshit. It's just that early chains designs were dumb.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious what other projects you're referring to that solved the scalability issues with no compromises?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Polkadot. Mina maybe first. Many zk roll ups. (all somewhat conventional looking threat models)
Omniledger paper was kinda early too. An implementation even exists, unsure if ever deployed. (80% honest)
All the false cases poses a problem here too..
Optimistic roll ups claim this. Imho they're wrong, but arguing that gets nasty: Alone, the word "secure" means "in threat models reasonable experts accept", not "in the threat model that favors my pet project." You need to write down their implicit assumptions before arguing they're unreaosnable. Afaik nobody ever bothered.
Payment channels claim this. Afaik they're secure, but not really scalable. Although easier, arguing this still becomes nasty.
Individual bridges between two chains cannot be called scalable, but if both chains have real finality then their threat model is 2/3 honest on both, not all necessarily so bad. A bridge ecosystem like cosmos becomes scalable, but wrecks this threat model. It's plauslbe however that cosmos' airdrop culture kinda adequately addressed this in practice, if only by dumb luck. Afak nobody ever surveyed zones' validator overlap. At least this should fall appart easily if you keep everything in theory land.