light-client VS DefinitelyTyped

The information arbitrage is pretty remarkable because they get a bunch of money for printing air tokens out of thin air and selling a portion of it. They then use the money mainly to control narratives. How many people even know that literally all eth traffic runs through central infura servers? Why? Because it doesn't scale without central servers. It also doesn't scale on-chain which is what they promised 7 years ago when they asked you to give them bitcoin to create a turing complete blockchain. They tried a lot of other stuff before roll-ups with centralized sequencers with trusted multisigs. They even tried to copy Lightning and funded Raiden network.

Examples: Bitcoin’s Lightning Network, Ethereum’s Raiden Network

Think of the blockchain as being the settlement layer between banks, and each roll-up or payment channel as its own bank.

Raiden Network - an instant payment solution with low fees compatible with all ERC-20 tokens.

Just an FYI: with Hub20 you can accept payments with any Ethereum-compatible blockchain and any scaling solution that uses the RPC interface (e.g, Polygon, Arbitrum, Optimism, Gnosis Chain). It also works with Raiden, which is akin to BTCs lightning network.

Except that anyone with a minimal involvement with Ethereum already knows that the base layer is not meant to be used on day-to-day operations.

We already learned about the decentralization trillema. The strategy to scale Ethereum through will be through the adoption of "layer-2" systems, where users are expected to be doing their transactions and avoid these costly transactions altogether.

There are roll-ups already dealing with NFT marketplaces [0]. There are roll-ups that can execute any type of ethereum smart contract [1] [2]. There are payment channels that allow completely decentralized and gas-less transfers of ERC-20 tokens [3].

[0] https://loopring.io

[1] https://optimism.io/

[2] https://offchainlabs.com/

[3] https://raiden.network

Raiden Network, ethereum's equivalent of lightning network, has been live on mainnet since 2020. It has little to no traction/usage as rollups are a much better scaling solution than state channels.

For those that are technical, the main selling point is its integration with layer-2 systems and support for multiple chains. It doesn't matter if you want to accept payment with Raiden or Arbitrum/Optimism, or xDAI/Polygon or BSC, your frontend does not change at all.

The point you are so reluctantly refusing to see is that it is about options and the long tail. Yeah, the majority of business and people are fine with the status quo. It doesn't mean that the rest should just conform.

> Other than that, unless you use Nano, every crypto transaction comes with a fee (...) slower than normal transactions

- https://raiden.network (near-zero fee transfers, akin to Lightning Network, running on Ethereum)

Raiden network is probably the closest equivalent of lightning network, but there are a couple of other projects using similar technology on Ethereum.

Prior to React 18, it used to include an implicit children prop, making it suitable for components expected to have children. For a long time, though, the implicit children prop type has been removed according to React 18's type changes.

Additionally, because TypeScript has a well established and widely used install-base, there are already many different definition files in the wild for supporting non-TypeScript supporting projects. One of the more extensive collections of these typings lives at the DefinitelyTyped repository, which publishes the package's community typings under the package names @types/your-package-name (where your-package-name is the name of the project you're looking for typings of) that you can look for on your package manager.

View on GitHub

Firefox maintain a library for unified extension API https://github.com/mozilla/webextension-polyfill

Their type definition for HAR request isn't exported https://github.com/DefinitelyTyped/DefinitelyTyped/blob/mast...

type NumberOrString = number | string; type Status = "idle" | "loading" | "success" | "failure" // React useState, can receive a value or a function as parameter to serve as initial value. // https://github.com/DefinitelyTyped/DefinitelyTyped/blob/a03856975a17eba524739676affbf70ac4078176/types/react/v17/index.d.ts#L920 function useState(initialState: S | (() => S)): [S, Dispatch>];

The TypeScript pull request was merged, so Sebastian (who helps maintain the React type definitions) exercised new powers in this pull request to the DefinitelyTyped repository for the React type definitions. At the time of writing, this pull request is still open, but once merged and shipped the React community we will feel its benefits.

there is an open issue: https://github.com/DefinitelyTyped/DefinitelyTyped/issues/61616

Relatively infrequently. Normally, if an npm package is popular and doesn’t have its own types, there will be a community provided types declaration file available from https://github.com/DefinitelyTyped/DefinitelyTyped