Repository navigation
Promote dev to main: native pool design, contracts Hyperion only - #57
Merged
Merged
Conversation
feat(frontend): refine navigation and adopt champagne accents
fix(ui): align QRL pairing with the ecosystem theme
chore(deps): use published connect-ui npm release
Integrate the native QRL pooled staking candidate after additional accounting/authentication reviews, bounded native VM property tests and the pending-refund discovery fix. Public-launch qualification remains separate.
Add native/DEPLOYMENT-TRANSPARENCY.md defining what every public deployment should publish: a manifest of addresses, source commit, compiler identity and runtime bytecode hashes; the fixed control model; the operator powers that remain; permitted native-QRL fund paths; and a reviewer verification checklist. Surface the same control model in the app so users see it before depositing: - StakePage: "What the operator cannot change" card and an "No upgrade authority" hero badge - HowItWorksPage: "Immutable by construction" section - LegalPage: "Operator control and contract immutability" section Each placement states both halves honestly -- no owner, upgrader, proxy admin, pauser, fund rescue, balance setter or mutable fee role, while validator signing (performance, penalties, execution-tip routing) remains an operational trust assumption. Link the template from the README alongside the security review. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RAKxypTyUJgDhHZbbcuS8C
…ncy-docs-u3tdud docs(transparency): publish deployment disclosure and control model
fix(frontend): keep transparency copy concise
* Align frontend with the QRL Blue design system Ports the wallet's QRL Blue palette and Inter numeric typeface into QuantaPool so the dApp reads as part of the same product family after the wallet's rebrand from Obsidian & Ember. Keeps the dApp's own scroll and layout deltas from the wallet (body as scroll container, no chart/sidebar tokens). Retokens the QuantaPool droplet mark from ember orange to the new sky-blue and ice-blue pair, and swaps the wallet-picker's MyQRLWallet icon for the current 3A mark instead of the SDK's baked EIP-6963 icon. Claude-Session: https://claude.ai/code/session_01LWKZ1b4FBetebjo1kcNHJ8 * Fix wallet-picker row overflow at narrow widths The rdns identifier sat beside the wallet name in one flex row with no min-w-0 or truncate, so a long value like com.qrlwallet.extension ran past the row and card border at 390px. Stacks the name and rdns vertically instead, each truncating independently within a min-w-0 flex-1 container. Claude-Session: https://claude.ai/code/session_01LWKZ1b4FBetebjo1kcNHJ8
* feat(wallet-picker): show MyQRLWallet as a single row MyQRLWallet announces itself twice over EIP-6963: com.qrlwallet.extension from the browser extension and com.qrlwallet.connect from the connect SDK, which covers the phone, web and desktop wallets. The picker listed both, so the user had to know which of two MyQRLWallet rows matched the wallet they actually have. groupMyQrlWallet() from @qrlwallet/connect-ui folds the pair into one row named MyQRLWallet, carrying the 3A mark. Clicking the row connects through the extension when it is installed, and a separate "Use phone or desktop app" button under it starts relay pairing. Without the extension the row itself starts relay pairing and there is no second button. The rdns line is replaced on that row by plain text naming the path a click takes. Every other announced wallet keeps its own row, its own icon and its own rdns line. The store's connect path is unchanged: both buttons hand a uuid to connectWallet(), which still resolves the transport from the rdns. The store imports the dependency-free @qrlwallet/connect-ui/wallets subpath because the store tests load this module in plain Node, where the package index would pull in the DOM pairing modal. Gates: npm run lint (zero warnings), npm run typecheck, npm test (42 pass), npm run build. Validated locally against a packed connect-ui 0.3.0. Claude-Session: https://claude.ai/code/session_01LWKZ1b4FBetebjo1kcNHJ8 * chore(deps): lock @qrlwallet/connect-ui 0.3.0 from the registry Claude-Session: https://claude.ai/code/session_01LWKZ1b4FBetebjo1kcNHJ8
Enable all strict compiler gates and type-aware lint enforcement through frontend CI. Validate wallet, RPC, contract and untyped library results before use, with no production assertions or rule exceptions. Preserve native wallet request bytes and add malformed-input regression coverage. All frontend gates pass, including 79 tests.
* chore: drop the last Solidity tooling, contracts are Hyperion only - Remove the unused Foundry forge-std submodule and the stale vendor/rocketpool entry in .gitmodules (it had no gitlink). - Move the Solidity-era Slither report to docs/legacy/ next to the V2 README that cites it. - README states that contracts are Hyperion only and that the Solidity sources and Foundry tests are retired. The retired-file record and the legacy dependency inventory list the removal. * docs: drop the fixed retired-path count from IMPLEMENTATION.md RETIRED-FILES.json now lists lib/forge-std as well, so the hard-coded total went stale. Link the record without a count.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings main up to dev. Main is the default branch, so it should show the current design. Until now it still showed the retired v2 contracts, including their Solidity sources.
Each change was reviewed and merged on dev. main has no commits of its own beyond earlier promotion merges. Nothing deploys from this merge.