* WIP on protobuf keys * Use Type() and Bytes() in sr25519 pub key Equals * Add tests * Add few more tests * Update other pub/priv key types Equals * Fix PrivKey's Sign method * Rename variables in tests * Fix infinite recursive calls * Use tm ed25519 keys * Add Sign and VerifySignature tests * Remove ed25519 and sr25519 references * proto linting * Add proto crypto file * Implement some of the new multisig proto type methods * Add tests for MultisigThresholdPubKey * Add tests for pubkey pb/amino conversion functions * Move crypto types.go and register new proto pubkeys * Add missing pointer ref * Address review comments * panic in MultisigThresholdPubKey VerifySignature * Use internal crypto.PubKey in multisig * Add tests for MultisigThresholdPubKey VerifyMultisignature * Only keep LegacyAminoMultisigThresholdPubKey and move to proto keys to v1 * Remove conversion functions and introduce internal PubKey type * Override Amino marshaling for proto pubkeys * Merge master * Make proto-gen * Start removal of old PubKeyMultisigThreshold references * Fix tests * Fix solomachine * Fix ante handler tests * Pull latest go-amino * Remove ed25519 * Remove old secp256k1 PubKey and PrivKey * Uncomment test case * Fix linting issues * More linting * Revert tests keys values * Add Amino overrides to proto keys * Add pubkey test * Fix tests * Use threshold isntead of K * Standardize Type * Revert standardize types commit * Fix build * Fix lint * Fix lint * Add comment * Register crypto.PubKey * Add empty key in BuildSimTx * Simplify proto names * Unpack interfaces for signing desc * Fix IBC tests? * Format proto * Use secp256k1 in ibc * Fixed merge issues * Uncomment tests * Update x/ibc/testing/solomachine.go * UnpackInterfaces for solomachine types * Remove old multisig * Add amino marshal for multisig * Fix lint * Correctly register amino * One test left! * Remove old struct * Fix test * Fix test * Unpack into tmcrypto * Remove old threshold pubkey tests * Fix register amino * Fix lint * Use sdk crypto PubKey in multisig UnpackInterfaces * Potential fix? * Register LegacyAminoPubKey * Register our own PubKey * Register tmcrypto PubKey * Register both PubKeys * Register interfaces in test * Refactor fiels * Add comments * Use anil's suggestion * Add norace back * Check nil * Address comments * FIx lint * Add tests for solomachine unpack interfaces * Fix query tx by hash * Better name in amino register * Display StdTx instead of proto Tx * Remove useless check Co-authored-by: Aaron Craelius <aaronc@users.noreply.github.com> Co-authored-by: blushi <marie.gauthier63@gmail.com> Co-authored-by: Alexander Bezobchuk <alexanderbez@users.noreply.github.com> Co-authored-by: colin axnér <25233464+colin-axner@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| adr-001-coin-source-tracing.md | ||
| adr-002-docs-structure.md | ||
| adr-003-dynamic-capability-store.md | ||
| adr-004-split-denomination-keys.md | ||
| adr-006-secret-store-replacement.md | ||
| adr-007-specialization-groups.md | ||
| adr-008-dCERT-group.md | ||
| adr-009-evidence-module.md | ||
| adr-010-modular-antehandler.md | ||
| adr-011-generalize-genesis-accounts.md | ||
| adr-012-state-accessors.md | ||
| adr-013-metrics.md | ||
| adr-014-proportional-slashing.md | ||
| adr-015-ibc-packet-receiver.md | ||
| adr-016-validator-consensus-key-rotation.md | ||
| adr-017-historical-header-module.md | ||
| adr-018-extendable-voting-period.md | ||
| adr-019-protobuf-state-encoding.md | ||
| adr-020-protobuf-transaction-encoding.md | ||
| adr-021-protobuf-query-encoding.md | ||
| adr-022-custom-panic-handling.md | ||
| adr-023-protobuf-naming.md | ||
| adr-024-coin-metadata.md | ||
| adr-025-ibc-passive-channels.md | ||
| adr-026-ibc-client-recovery-mechanisms.md | ||
| adr-027-deterministic-protobuf-serialization.md | ||
| adr-template.md | ||
| README.md | ||
| readme.md~origin_master-docs | ||
| order | parent | ||
|---|---|---|---|
| false |
|
Architecture Decision Records (ADR)
This is a location to record all high-level architecture decisions in the Cosmos-SDK.
You can read more about the ADR concept in this blog post.
An ADR should provide:
- Context on the relevant goals and the current state
- Proposed changes to achieve the goals
- Summary of pros and cons
- References
- Changelog
Note the distinction between an ADR and a spec. The ADR provides the context, intuition, reasoning, and justification for a change in architecture, or for the architecture of something new. The spec is much more compressed and streamlined summary of everything as it stands today.
If recorded decisions turned out to be lacking, convene a discussion, record the new decisions here, and then modify the code to match.
Note the context/background should be written in the present tense.
Please add a entry below in your Pull Request for an ADR.
ADR Table of Contents
- ADR 001: Coin Source Tracing
- ADR 002: SDK Documentation Structure
- ADR 003: Dynamic Capability Store
- ADR 004: Split Denomination Keys
- ADR 006: Secret Store Replacement
- ADR 009: Evidence Module
- ADR 010: Modular AnteHandler
- ADR 011: Generalize Genesis Accounts
- ADR 012: State Accessors
- ADR 013: Metrics
- ADR 015: IBC Packet Receiver
- ADR 016: Validator Consensus Key Rotation
- ADR 017: Historical Header Module
- ADR 018: Extendable Voting Periods
- ADR 019: Protocol Buffer State Encoding
- ADR 020: Protocol Buffer Transaction Encoding
- ADR 021: Protocol Buffer Query Encoding
- ADR 022: Custom baseapp panic handling
- ADR 023: Protocol Buffer Naming and Versioning
- ADR 024: Coin Metadata
- ADR 025: IBC Passive Channels
- ADR 026: IBC Client Recovery Mechanisms
- ADR 027: Deterministic Protobuf Serialization