christn

Results 38 issues of christn

A new section / set of widgets dedicated to Layers 2 and their effect on the burn / eth supply Could include: - Time series graphs depicting following metrics over...

Some contracts on the burn leaderboard are missing labels / twitter info even though the info should be available. For example [this contract](https://etherscan.io/address/0xe87753eb91d6a61ea342bb9044a97764366cc7b2#readProxyContract) seems to belong to the "Tinfun" nft...

The MEV Share of the Validator Rewards is currently hard coded. We could replace that with a dynamic calculation Examples for such calculation elsewhere: - https://transparency.flashbots.net/ - https://mevboost.pics/ ![image](https://github.com/ultrasoundmoney/frontend/assets/15629702/b1389568-b294-4e5a-860a-e5f3823e9b5d)

The values in the "Gas Streak" widget, seem to be wrong in certain cases. TODO: @JustinDrake Could you maybe give some more detail / examples on this ? ![image](https://github.com/ultrasoundmoney/frontend/assets/15629702/367e8afc-d503-4544-88d7-c3f3777efc40)

There are inconsistencies in design details such as differents fonts being used in different parts of the website ? @JustinDrake Feel free to add concrete examples / screenshots here, where...

Currently the website supports different timeframes: Eth-Supply Graph: `5m, 1h, 1d, 7d, 30d, since merge` All other graphs / tables: `5m, 1h, 1d, 7d, 30d, since burn` Suggestion: - [...

While trying to implement a `cast` command to migrate a contract verification from on explorer to another (specifically from etherscan to blockscout), I encountered the issue that the `contract_source_code` and...

### Describe the bug On the [documentation for "accounts" ](https://ethereum.org/en/developers/docs/accounts/) it says: > _An Ethereum account is an entity with an ether (ETH) balance that can send transactions on Ethereum....

bug 🐛
low priority

- Add separate installation of solidity 0.8 compatible openzeppelin contracts (containing both EIP712 and ERC20Snapshots) - Add script to remove duplicate type definitions from contracts used in both oz libraries...