sudo rm -rf --no-preserve-root / (@pcaversaccio) 's Twitter Profile
sudo rm -rf --no-preserve-root /

@pcaversaccio

๐–๐จ๐ซ๐ค๐ข๐ง๐  ๐จ๐ง ๐ฐ๐ก๐š๐ญ'๐ฌ ๐ง๐ž๐ฑ๐ญ.
๊ŸผG๊Ÿผ: 063E 966C 93AB 4356 492F E032 7C3B 4B4B 7725 111F

ID: 113203570

linkhttps://github.com/pcaversaccio calendar_today11-02-2010 01:40:28

24,24K Tweet

25,25K Followers

333 Following

sudo rm -rf --no-preserve-root / (@pcaversaccio) 's Twitter Profile Photo
sudo rm -rf --no-preserve-root /
@pcaversaccio

6 months ago

Alright folks, a new nice update was just shipped to the safe-tx-hashes-util script. Some security councils use so-called nested Safes as signers (i.e. use a Safe as a signatory to another Safe). When a nested Safe needs to approve a transaction on the primary Safe, it must call

Alright folks, a new nice update was just shipped to the safe-tx-hashes-util script. Some security councils use so-called nested Safes as signers (i.e. use a Safe as a signatory to another Safe). When a nested Safe needs to approve a transaction on the primary Safe, it must call