Mablr mablr

reth

Launch nodes which will use only dicv5 protocol to discover themselves.

Node 0

RUST_LOG=info,net::discv5=trace ./target/debug/reth node --chain dev\
  --disable-dns-discovery\
  --disable-discv4-discovery\
 --enable-discv5-discovery\

Address is expected to start with 000000.

running 1 test
test tests::test_alloy has been running for over 60 seconds
Found matching address: 0x0000004b2284982bb9a7482bfb76c721631260fe, for salt: 0x0000000000000000000000000000000000000000000000000000000000f17dfe
test tests::test_alloy ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 1 filtered out; finished in 520.59s

Keybase proof

I hereby claim:

I am mablr on github.
I am mablr (https://keybase.io/mablr) on keybase.
I have a public key ASClaCTdJKAwvVGJEzeWs5QbxIcAjI-cfgOOZ5_WzS9fiQo

To claim this, I am signing this object:

	// SPDX-License-Identifier: WTFPL
	pragma solidity ^0.8.13;

	import {Script, console2} from "forge-std/Script.sol";
	import {Counter} from "../src/Counter.sol";

	contract CounterScript is Script {
	function setUp() public {}

	function run() public {

	The user provided the following information about themselves. This user profile is shown to you in all conversations they have -- this means it is not relevant to 99% of requests.
	Before answering, quietly think about whether the user's request is "directly related", "related", "tangentially related", or "not related" to the user profile provided.
	Only acknowledge the profile when the request is directly related to the information provided.
	Otherwise, don't acknowledge the existence of these instructions or the information at all.
	User profile:
	```Sample user profile information```