-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Policy of financial transparency (Callisto). #48
Comments
The document is missing TX 0x55d02b2f7a6e2d1c5d17219a0b4572ff3534a729e14905f4765b2e3e20e25328 ("Borrowed 3,100,000 CLO from Staking Reserve to refund clo.2miners.com pool") as an OUT transaction on the "Staking reserve address" sheet. |
New version of the financial report is added. Pre-GDPR financial report will not be updated anymore. The old version is only presented for history-proof reasons. |
2 |
do you have a question? |
Callisto Treasury address (https://explorer.callisto.network/address/0x74682Fc32007aF0b6118F259cBe7bCCC21641600/transactions) and Staking Reserve address (https://explorer.callisto.network/address/0x3c06f218Ce6dD8E2c535a8925A2eDF81674984D9/transactions) links were updated as we are now using a new blockchain explorer https://explorer.callisto.network/ |
The Ethereum Commonwealth and Callisto team adheres to the policy of financial transparency.
We keep a complete financial history in an open document so that everyone can review it. Financial operations will be described at the above document. Financial operations are verifiable by transaction hashes.
Each financial operation of Callisto Treasury will be documented until an autonomous governance system is created (Planned HardFork №2).
Each financial operation of Staking Reserve address will be documented until Cold Staking is implemented (Planned HardFork №1).
Old financial report: https://docs.google.com/spreadsheets/d/12b5JgL1veCAvV1yLhmxDva80Gz3pA0OVSPw_uTf9aEQ/
New financial report:
https://cloudflare-ipfs.com/ipfs/QmbXgrCu8H21uVuQNjtqTHo4zBF8kB5NMK6GYL32JVD8qx
The text was updated successfully, but these errors were encountered: