With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js. Learn more →
Portal-network-specs Alternatives
Similar projects and alternatives to portal-network-specs
-
Joplin
Joplin - the secure note taking and to-do app with synchronisation capabilities for Windows, macOS, Linux, Android and iOS.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
rotki
A portfolio tracking, analytics, accounting and management application that protects your privacy
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
annotated-spec
Vitalik's annotated eth2 spec. Not intended to be "the" annotated spec; other documents like Ben Edgington's https://benjaminion.xyz/eth2-annotated-spec/ also exist. This one is intended to focus more on design rationale.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
portal-network-specs reviews and mentions
-
Signal founder’s constructive criticism of web3
Other blockchain networks struggle because it's not trivial for wallets to have embedded nodes. It's not even really easy to do on Ethereum since light clients are hard to use, but this is improving with better infrastructure. The other hurdle for the Ethereum ecosystem is the reliance on the web stack, which trains users that the default way to interact with these networks is through a web browser, which is another limiting factor for being able to run your own node. And so yeah, obviously people will rely on Infura. But it doesn't have to be like that, this is a just result of the technology being limited (irrationally self-imposed, with the reliance on web browsers) rather than users' true desires.
-
POKT was one of the most interesting projects on ETH Denver, POKT North Star (v1) release is going to help decentralize the entire web3 in a big way
The solution is to build a different structure that eliminates the antagonistic relationships between the parties, where there's no economic advantage to scale. There's this project directly backed by EF doing that but that doesn't have VC backing and there's no token so obviously there's no hype machine pushing it along.
-
Web3APIs vs Ethers.Js?
Or better, eventually, do in a distributed way with something like the portal network: https://github.com/ethereum/portal-network-specs
- Daily General Discussion - January 9, 2022
-
My First Impressions of Web3
From the post:
> People don’t want to run their own servers, and never will...
Fair enough, but there are active efforts to develop ultra-light clients for Ethereum together with the concept of "portal network":
https://github.com/ethereum/portal-network-specs/
https://our.status.im/nimbus-fluffly/
> there’s not even a word for an actual untrusted client/server interface that will have to exist somewhere, and no acknowledgement that if successful there will ultimately be billions (!) more clients than servers.
I would not say there's "no acknowledgement" of this; depending on how deep you are in the space, it's pretty obvious that the goal is to have layered networks and mission specific networks (storage vs. messaging vs. consensus), all economically incentivized, that are p2p through and through, from the resource constrained devices of end consumers to the staking nodes that secure the networks. That's the hope, the goal, and the focus of ongoing efforts.
The opposite of the missing word is "a node in a p2p network".
The points made about the difficulty in evolving protocols quickly are not lost on me, but I guess I'm more optimistic than the author that it will happen relatively quickly in coming years, including this one. In the process, there will be opportunities seized where the protocols fall short and half-measures or worse (with respect to decentralization) will generate excitement for a time. That seems like "growing pains" to me.
- The Portal Network
-
Impromptu technical AMA on history expiry
Older blocks, transactions and receipts/logs would still be accessible through dedicated sub-protocols (eg. the Portal Network) or externally developed protocols (eg. TheGraph), in addition to a much smaller but still sufficient number of volunteer nodes and block explorers. Note that many dapps are already moving their historical data queries to TheGraph and similar protocols for efficiency.
-
State Network DHT - Development Update #2 - Eth1.x Research
Does this help? https://github.com/ethereum/stateless-ethereum-specs/wiki/Glossary
-
Making the ecosystem more light-client friendly
Reorganize the p2p network to make providing proofs simpler and cheaper; see Piper Merriam's work on this.
-
Weak statelessness and/or state expiry: coming soon (x-post from EthMagicians)
Piper Merriam's work on distributed state storage and state and witness availability: https://ethresear.ch/t/scalable-transaction-gossip/8660 and https://github.com/ethereum/stateless-ethereum-specs/pull/54
-
A note from our sponsor - SurveyJS
surveyjs.io | 29 Apr 2024
Stats
The primary programming language of portal-network-specs is JavaScript.
Popular Comparisons
- portal-network-specs VS iroha
- portal-network-specs VS nft.storage
- portal-network-specs VS moonworm
- portal-network-specs VS go-ethereum
- portal-network-specs VS rotki
- portal-network-specs VS research
- portal-network-specs VS ethereum-org-website
- portal-network-specs VS PageSigner
- portal-network-specs VS annotated-spec
- portal-network-specs VS arweave
Sponsored