Skip to content
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

Prepare Namadillo for v0.1 release #863

Open
47 of 50 tasks
pedrorezende opened this issue Jun 11, 2024 · 1 comment
Open
47 of 50 tasks

Prepare Namadillo for v0.1 release #863

pedrorezende opened this issue Jun 11, 2024 · 1 comment

Comments

@pedrorezende
Copy link
Contributor

pedrorezende commented Jun 11, 2024

This issue lists the remaining tasks for the first release version for Namadillo (v0.1).

General

Staking

Governance

  • Don't add proposal JSON modal to browser history #806 - Bug, non-blocking for release
  • Use dates instead of epochs for proposal times
  • Add finalized text to VoteHelpText component #798
    • Temporarily removed panel. Not essential for release.
  • Readd search/filtering on the proposals table
  • Toast doesn't react to proposal vote transaction being successful
  • Turnout doesn't seem to be right
    • Not sure what I was seeing but it seems fine now
  • Review number of http queries on Governance page
    • Removed redundant queries when fetching all proposals

Extension/SDK

  • Extension: UI - Update button border radius for consistency #1000 UI update for buttons
  • Support Namada 0.40.0 (if 0.41.0 becomes launch version, uncheck this and update)
  • Implement signing updates for Ledger - This will need to be updated once Ledger App is working on Namada v0.40.0!
  • UI Tweaks on list of Tx details
  • Prepare release for the stores
  • Implement Tx batch signing
  • Add back Tx details

Indexer

  • Add query for wasm code paths + wasm checksum hashes (In progress: SDK/Indexer: Use indexer for fetching tx code checksums #923)
  • Return status of a bond
  • Getting status as "pending" after the start epoch - intermittent
  • Create endpoint to query chainId, rpcUrl, and nativeToken
  • Proposal startTime and endTime change on every call - Comment(@mateuszjasiuk) - this will change as we can only estimate time of future epochs
  • Proposal IDs should start from 0, not 1 - intermittent
  • Fee estimation endpoint
@euharrison
Copy link
Contributor

euharrison commented Aug 7, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment