EthSecurity – Telegram
https://ethnoscriptions.com

It's cheaper and more decentralized than using contract storage.

Also protocol guarantees global uniqueness of the content of all valid Ethnoscriptions!

Plus it's skating to where the puck is going in an L2 world. https://ethereumpunks.net
@EthSecurity1
🔥3
EthSecurity
https://ethnoscriptions.com It's cheaper and more decentralized than using contract storage. Also protocol guarantees global uniqueness of the content of all valid Ethnoscriptions! Plus it's skating to where the puck is going in an L2 world. https://ethereumpunks.net…
ESIP-1: Smart Contract Support

Specification

Incorporate two new smart contract events into the Ethnoscriptions Protocol:

- TransferEthnoscription(address indexed recipient, bytes32 indexed ethnoscriptionTxHash)

- CreateEthnoscription(address indexed initialOwner, string dataURI)

When a contract emits TransferEthnoscription, the protocol should register a valid ethnoscription transfer from the contract to recipient of the ethnoscription created in transaction hash ethnoscriptionTxHash, provided the contract owns that ethnoscription when emitting the event.

When a contract emits CreateEthnoscription, the protocol should register a valid ethnoscription creation, provided the dataURI is valid and unique. The initial owner will be initialOwner.

Rationale

Ethnoscriptions can be transferred to any address, which means smart contracts can own them. However, smart contracts cannot currently transfer or create ethnoscriptions themselves.

This inhibits the creation of protocol-native apps that require smart contracts, such as marketplaces. Further, it makes the protocol difficult to use for smart contract wallet users.

This proposal lays out a simple and low gas mechanism for enabling smart contracts to transfer and create ethnoscriptions, thereby creating parity between smart contracts and EOAs under the protocol.

Indexing these events across all contracts increases the burden of operating an indexer, but this extra cost is incremental given that indexers must inspect the calldata of every transaction anyway.
⚙️what triggers the creation would be the calldata of the transaction where you told the contract to do that—only that transaction gets a real transaction hash, which is the ethnoscription id.
@EthSecurity1
21
Last week, Shido Global was exploited on BSC through a flash loan attack, allowing the attacker to steal around 977 WBNB from the pool. https://explorer.phalcon.xyz/tx/bsc/0x72f8dd2bcfe2c9fbf0d933678170417802ac8a0d8995ff9a56bfbabe3aa712d6I
@EthSecurity1
🔥4😢1
These results are from a 1-hour long bot-race & not a full-fledged audit.

Wake up to the reality anon, ChatGPT & bots will soon eradicate the lower rungs of bugs from any codebase.

Only the auditors that dare to dive deep will survive this battlefield.

https://gist.github.com/liveactionllama/27513952718ec3cbcf9de0fda7fef49c
@Ethsecurity1
5
6👍1
Forwarded from Rektoff
Gm Rektoffians!
We’ve prepared an alpha-only web3 security telegram pack so you can always stay up to date with market trends, cool articles and useful groups 👥

Add it with the following link:
https://news.1rj.ru/str/addlist/b0NZzSm3Q9gxYTMy

And feel free to share your gem channels under this post in case we missed something.

Stay Rektoff😀
Please open Telegram to view this post
VIEW IN TELEGRAM
🫡5
still stuck using csv? well there’s a new tool for anyone that enjoys rust, parquet, or crypto data…

❄️🧊cryo🧊❄️

you can use cryo to easily extract:
- blocks
- txs
- logs
- call traces
- slot traces
- balance traces
- nonce traces
- code traces
- vm traces

cryo can extract all historical uniswap trades with this command:

cryo logs --topic0 0xc42079f94a6350d7e6235f29174924f928cc2ac818eb64fed8004e115fbcca67

@EthSecurity1
🔥6👍2