Translate EVM bytecode into opcodes using pure Regex :)
Demo: https://twitter.com/0x796/status/1608039943582142464
Try here: https://regex101.com/
Use PCRE2 (Perl compatible) Regex flavor.
Search:
Translate EVM bytecode into opcodes using pure Regex :)
Demo: https://twitter.com/0x796/status/1608039943582142464
Try here: https://regex101.com/
Use PCRE2 (Perl compatible) Regex flavor.
Search:
Syncing an Ethereum node is largely reliant on IOPS, I/O Per Second. Budget SSDs will struggle to an extent, and some won't be able to sync at all.
This document aims to snapshot some known good and known bad models.
The drive lists are ordered by interface and then by capacity and alphabetically by vendor name, not by preference. The lists are not exhaustive at all. @mwpastore linked a filterable spreadsheet in comments that has a far greater variety of drives and their characteristics. Filter it by DRAM yes, NAND Type TLC, Form Factor M.2, and desired capacity.
For size, 4TB comes recommended as of mid 2024. The smaller 2TB drive should last an Ethereum full node until early 2025 or thereabouts, with crystal ball uncertainty. Remy wrote a migration guide to 4TB.
The loading-states
extension allows you to easily manage loading states while a request is in flight, including disabling elements, and adding and removing CSS classes.
Add the hx-ext="loading-states"
attribute to the body tag or to any parent element containing your htmx attributes.
Add the following class to your stylesheet to make sure elements are hidden by default:
import { useState, useEffect } from 'react' | |
import Web3 from 'web3' | |
const [account, setAccount] = useState(null) | |
let [web3, setWeb3] = useState(null) | |
useEffect(() => { | |
checkAccount() | |
}, []) | |
// invoke to connect to wallet account |
Peter Naur's classic 1985 essay "Programming as Theory Building" argues that a program is not its source code. A program is a shared mental construct (he uses the word theory) that lives in the minds of the people who work on it. If you lose the people, you lose the program. The code is merely a written representation of the program, and it's lossy, so you can't reconstruct
import pandas as pd | |
import numpy as np | |
def test_cutoffs(start_amount, start_price, buy_fee, sell_fee, end_price): | |
bought_fee = start_amount*buy_fee | |
bought_amt = (start_amount-bought_fee) / start_price | |
sold = bought_amt*end_price | |
sold_fee = sold*sell_fee | |
sold = sold-sold_fee |
#!/usr/bin/env python3.5 | |
from time import time | |
import dask.dataframe as dd | |
import pandas as pd | |
from cassandra.cluster import Cluster | |
from cassandra.concurrent import execute_concurrent | |
from cassandra.policies import ConstantReconnectionPolicy |
Facades are a programming pattern in which a simpler public interface is provided to mask a composition of internal, more-complex, component usages.
When writing a lot of NgRx code - as many enterprises do - developers quickly accumulate large collections of actions and selectors classes. These classes are used to dispatch and query [respectively] the NgRx Store.
Using a Facade - to wrap and blackbox NgRx - simplifies accessing and modifying your NgRx state by masking internal all interactions with the Store
, actions
, reducers
, selectors
, and effects
.
For more introduction, see Better State Management with Ngrx Facades
$white: #ffffff; | |
$black: #000000; | |
$red50: #ffebee; | |
$red100: #ffcdd2; | |
$red200: #ef9a9a; | |
$red300: #e57373; | |
$red400: #ef5350; | |
$red500: #f44336; | |
$red600: #e53935; | |
$red700: #d32f2f; |