Timeline for Clearing RAM tables of eosio.token contract
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 21, 2019 at 18:24 | history | edited | Andres Berrios | CC BY-SA 4.0 |
Update code to work with latest version of eosio.cdt
|
| Jul 19, 2018 at 17:31 | comment | added | Andres Berrios | I know. I might write a contract to allow you to prove that you did, but in a way you would be throwing away a good feature that EOSIO has, for managing, updating, and fixing contracts. I think it would make more sense to make a system for managing contracts in a decentralized way. | |
| Jul 19, 2018 at 16:59 | comment | added | confused00 | yeah but you can't prove you did... | |
| Jul 19, 2018 at 16:51 | comment | added | Andres Berrios | @confused00 well, in theory you could simply deploy it and throw away the key lol | |
| Jul 19, 2018 at 14:23 | comment | added | confused00 | yeah, that sucks. it'd be nice if there was an option to deploy an immutable contract. doesn't seem too hard to implement on the existing code base and it would help a lot with trust issues for some contracts that require it more than they require bug fixes | |
| Jul 19, 2018 at 14:17 | comment | added | Andres Berrios | @confused00 yes, the contract account can update its contract whenever it wants and modify the data however it wants. Sadly, this is actually very centralized, as it puts all the power on the contract account's hands, and for a truly decentralized dapp administration you would need to make that account an "organization", managed by the community itself and not a central developer. | |
| Jul 19, 2018 at 9:18 | comment | added | confused00 | so any token that was already airdropped can be updated at any point by the creator and delete everyone else's tokens? | |
| Jul 17, 2018 at 23:31 | vote | accept | Damir Olejar | ||
| Jul 17, 2018 at 23:30 | history | bounty ended | Damir Olejar | ||
| Jul 17, 2018 at 21:46 | comment | added | tmm♦ | Nice, this is way better than the previous posted solution! Cheers! | |
| Jul 17, 2018 at 20:10 | comment | added | Damir Olejar | Andres, AWESOME... I will be testing this in a few hours. Cheers mate, and thank you for contacting me directly. | |
| Jul 17, 2018 at 20:05 | history | edited | Andres Berrios | CC BY-SA 4.0 |
Corrected a claim in one of the issues of the other solution
|
| Jul 17, 2018 at 19:47 | history | answered | Andres Berrios | CC BY-SA 4.0 |