Notice
Recent Posts
Recent Comments
Link
| 일 | 월 | 화 | 수 | 목 | 금 | 토 |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 | 30 |
Tags
- web3
- ethereum
- openzepplin
- ethernaut
- Coin
- Wargame
- web assembly
- Block
- soft fork
- audit
- approve
- syntax
- coin flip
- libray
- solidity
- TransferFrom
- Smart contract
- tx.origin
- byte code
- Assembly
- NaughtCoin
- Ethererum
- secureum
- hard fork
- EVM
- ethereum virtual machine
- transaction
- writeup
- chain reorganization
- Oracle Cloud
Archives
- Today
- Total
목록fallout (1)
c0mpos3r
1. 문제 분석That was silly wasn't it? Real world contracts must be much more secure than this and so must it be much harder to hack them right? Well... Not quite.The story of Rubixi is a very well known case in the Ethereum ecosystem. The company changed its name from 'Dynamic Pyramid' to 'Rubixi' but somehow they didn't rename the constructor method of its contract:contract Rubixi { address private..
Web3/Hacking
2025. 8. 24. 22:16