compound-protocol
cosmos
Our great sponsors
compound-protocol | cosmos | |
---|---|---|
16 | 2 | |
1,819 | 1,246 | |
0.7% | 2.3% | |
0.0 | 0.0 | |
4 months ago | 4 months ago | |
TypeScript | TeX | |
BSD 3-clause "New" or "Revised" License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
compound-protocol
- List of smart contracts to strengthen your Auditing skills
-
How to set max votes on DAO delegation?
I'm making an NFT crowdfunding protocol as a summer project and am using Compound Governance contract along with ERC20Votes to do so.
-
Cryptocurrency Loan Platform Implodes in $130M Hack
Yep however I don't think I'd consider it to quite the same extreme. No doubt it was bad however proportionally to the size of the platform Cream's exploit was far more damaging. Like the rekt.news post mentions, it was more of a banking/spec error than an outright vulnerability. Your spec can't protect you if the loss is due to intended behaviour. There are ways to mitigate this however. The main way is by making your spec concise and clearly representable as a series of state transitions & operations or as a series of transformations.
The Compound Finance paper spec essentially just lists "this subsystem does these things" and then each function/operation is a list of preconditions, what actions are taken in what conditions, and the expected result. This isn't bad per se but it's not great either. Instead the paper spec really should be showing what transformation is being applied to the state, why we want that transformation applied, what properties must hold throughout the transformation, and then demonstrating that those properties hold.
Compare this (Compound):
https://github.com/compound-finance/compound-protocol/blob/m...
-
Daily General Discussion - July 11, 2021
Today I've been integrating Compound's Governor Bravo with my token and I just wanted to share how much fun I've had!
- [Discussion] Use cases for IBC
cosmos
-
[Discussion] Use cases for IBC
This is probably a question better suited to be asked to one of the developers, as most people here are not developers, and honestly each developer will likely have a different answer for what they want to do with IBC. It can hard to abstract this information from where it is available. First, you could reread the Cosmos white paper that has use-cases for IBC inside of it. https://github.com/cosmos/cosmos/blob/master/WHITEPAPER.md#inter-blockchain-communication-ibc
What are some alternatives?
ics - Interchain Standards (ICS) for the Cosmos network & interchain ecosystem. [Moved to: https://github.com/cosmos/ibc]
security - Some of my security stuff and vulnerabilities. Nothing advanced. More to come.
verified-smart-contracts - Smart contracts which are formally verified
verified-smart-contra
security - Materials related to security: docs, checklists, processes, etc...
publications - Publications from Trail of Bits
ethereum-burn-stats - Website that showcases EIP-1559 Burn
cosmos-auto-rewards - Cosmos Hub script for reinvest rewards automatically (Stargate)
art-gobblers - An experimental decentralized art factory by Justin Roiland and Paradigm.
ProteaV2Contracts
Publications - Misc. publications, conference slides, etc. For more, go to http://BartoszMilewski.com
ibc - Interchain Standards (ICS) for the Cosmos network & interchain ecosystem.