Comments (3)
Thanks for keeping this open. 👍
from solidity.
On that line of thought, it'd be great to have something explaining how long transaction logs are kept around to be accessed by web3's filters or similar mechanisms.
I thought they were permanent, but the 256 block limitation on accessing block hashes makes me wonder if that's really the intent.
The persistence of events can make a fairly large difference in the way external code will interface with contracts, so clarity there would be really useful.
from solidity.
I asked Vitalik about this. He said logs are stored forever although in future it'll be down to individual nodes (who I suggested could just for archive access). The longevity of logs and contracts is important to DAPs so I would also like to see more documentation on this.
from solidity.
Related Issues (20)
- Add nuances of .codehash usage to the documentation HOT 1
- Extract tests in `test/libsolidity/ViewPureChecker.cpp` to `syntaxTests/viewPureChecker` HOT 1
- `payable` declaration defaults function to `public` visibility HOT 2
- solc produce Different Bytcode in multiple contracts after an equivalent expression change HOT 5
- Enable Discussions In This Repository HOT 1
- SMTChecker support for EIP-6780: SELFDESTRUCT only in same transaction
- New macOS Universal Binaries are signed HOT 4
- Incoherence in compiler output and CHC encoding produced by SolCMC
- Fix release docker build (alpine) and add a nightly CI run HOT 1
- Remove EIP-1153 Warning HOT 3
- Emscripten binaries in solc npm package and in solc-bin are not identical
- Function "tstore" not found HOT 2
- Security Vulnerability in Ethereum Smart Contracts HOT 6
- ABI is different for functions defined in libraries as compared to contracts.
- Function overload clash for custom types
- version pragma accepts partial string literals in any position
- Outputting the CBOR Metadata positions in the bytecode
- Introduce `readonly` modifier for internal function parameters in memory
- Shift in AST IDs affects inlining and expression splitting decisions in Yul Optimizer, causing bytecode differences HOT 1
- [TypeChecker] ICE in memoryMemberTypes() HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from solidity.