web3.js
polkadot
web3.js | polkadot | |
---|---|---|
30 | 143 | |
18,780 | 7,026 | |
0.8% | - | |
9.3 | 9.7 | |
7 days ago | 8 months ago | |
TypeScript | Rust | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
web3.js
-
Projects to contribute to
Web3.js (16500 GitHub Stars) https://github.com/web3/web3.js/
-
DeFi development learning
- https://github.com/web3/web3.js - Web3 JavaScript
-
How Trezor’s partnership with Wasabi Wallet could open doors for privacy solutions in the Web3 space.
last I checked web3.js only supports EVM coins / tokens. Was there an announcement I missed?
-
Frame size of "X" bytes exceeds maximum accepted frame size
I have attempted to increase the maxReceivedFrameSize in my truffle-config, which is a solution offered here like so:
-
Need the state of every contract at a point in 2016
Here is a way to do this using web3.js.
-
Exploring the Coinbase API From a Web2 Starting Point
Since we will build a Web3 example, the web3 framework was installed using npm (other options can be found here):
- How do I reduce the bundle size of external libraries?
-
Median webpage size was 2.3 MB in July 2022
yeah, I could see that.
web3.js is a super bloated library and will be added more frequently unless a team does a more optimal version from scratch
https://github.com/ChainSafe/web3.js/issues/1178
- Alpha of Web3.js v4 Just Released
polkadot
-
Projects to contribute to
Polkadot (6400 GitHub Stars) https://github.com/paritytech/polkadot
-
There are 43 active parachains on Polkadot, not counting private ones, and 130 total announced projects headed for parachain status. When is the relay chain going to be upgraded to handle more than 100 parachains?
I don't think asynchronous backing has any direct effect on the number of parachains, no (I mean, there likely is an effect, but it's not the goal and my understanding is that any effect on that would be minimal, although I'm not involved in the deep engineering here). It increases throughput, correct, by decreasing the time between blocks by not needing to do a "roundtrip" to the relay chain to build new blocks. See https://github.com/paritytech/polkadot/issues/3779 for an overview.
-
Polkadot Staking Alternatives in light of Kraken US's staking closure
"The 27 waiting day is unavoidable and a very important security measure to protect against certain attacks and vulnerabilities of PoS. I totally understand that it is annoying, but arguably it is for the benefit+security of the overall network, which includes you as well at the end of the day as DOT-holder." - from this GitHub discussion.
- Polkadot Surpasses Cardano To Rank Top In Crypto Development Activity
-
Can we change the 28 day unbonding lockup period?
Ref: Kianenigma @ https://github.com/paritytech/polkadot/issues/2418
-
Polkadot Digest 19 Jan 2023
Polkadot 0.9.37 has been released with MEDIUM upgrade priority. https://github.com/paritytech/polkadot/releases/tag/v0.9.37
- Minimum Active Bond jumped from 237 to 248.5 in 8 eras :(
-
Polkadot Digest 17 Jan 2023
Specifically, it was this PR that changed it: https://github.com/paritytech/polkadot/pull/6230
-
Question about controller address when staking.
Actually it looks like you can! It's just not recommended. This is from the official documentation: "Starting with runtime version v23 natively included in the client version 0.8.23, payouts can go to any custom address. If you'd like to redirect payments to an account that is neither the controller nor the stash account, set one up. Note that setting an exchange address as the recipient of the staking rewards is extremely unsafe.*
-
Bill Laboon AMA 9 Dec 2022 - 14.00-15.00 UTC
A particular validator sent out a LOT of dispute reports (i.e., saying that other validators did something incorrectly) last night (for reasons unknown). It looks like other nodes "choked" reading all of these disputes, and one subsystem died, stalling nodes but NOT killing the process. It's still being investigated, but you can look at the issue on Github to see it being discussed here: https://github.com/paritytech/polkadot/issues/6412
What are some alternatives?
web3-react - A simple, maximally extensible, dependency minimized framework for building modern Ethereum dApps
substrate - Substrate: The platform for blockchain innovators
matic-gas-prices - Displays current gas prices on the Polygon (MATIC) network.
parity-signer - Air-gapped crypto wallet.
opensea-js - TypeScript SDK for the OpenSea marketplace
ledger-kusama - Kusama app for Ledger Nano S and X
gleam - ⭐️ A friendly language for building type-safe, scalable systems!
rust - Rust language bindings for TensorFlow
abi-decoder - Nodejs and Javascript library for decoding data params and events from ethereum transactions
Parity - (deprecated) The fast, light, and robust client for the Ethereum mainnet.
Blitz - ⚡️ The Missing Fullstack Toolkit for Next.js
cumulus - Write Parachains on Substrate