You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This defines a set of encoding rules for Protocol Buffers 3 (proto3) for serializing messages deterministically
such that the serialized form is suitable for signing and encoding in cryptographic attestations (ex. Merkle trees).
Similar to ASN.1 and
Cap'n Proto, a set of "canonical encoding rules" (CER)
is used to define a canonical encoding where the basic proto3 specification does not do so. In this sense,
the default protocol buffers specification provides a set of "basic encoding rules" which are not deterministic,
and we extend that specification to support deterministic encoding for cryptographic use cases.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Regen Network, and our compatriots from TruStory, IOV, Althea and Wallet Connect combined forces to become Team Gaians for the Berlin HackAtom. This blog will review what we created and what it can be used for.
Our team focused on hacking towards a clear use case: user friendly participation in smart contracts about ecological health. In order to create usable functionality for this the team had to overcome some key challenges: create a smart contracting framework for the Cosmos SDK and improved key management.
And that is exactly what was accomplished. In 36 hours, the team pulled together an incredibly powerful and flexible, smart contracting module using WebAssembly (Wasm) and key management modules that interact to create platform that is more powerful and robust than Ethereum, and built in the Cosmos SDK, making interoperability with other chains easy.
Let’s walk through the functionality that was built using the use-case we considered - a simple three-party contract for Regen Netw
The delegation module also allows for fee delegation via some
changes to the AnteHandler and StdTx. The behavior is similar
to that described above for Msg delegations except using
the interface FeeAllowance instead of Capability:
// FeeAllowance defines a permission for one account to use another account's balance// to pay fees