-
Notifications
You must be signed in to change notification settings - Fork 47
Open
Labels
enhancementNew feature or requestNew feature or request
Description
User Story
As a developer at Noblocks, I want to integrate Starknet as a supported network using Privy’s Tier 2 chain support, so that our users can transact on Starknet using their existing embedded wallets.
Acceptance Criteria
GIVEN the Noblocks application environment.
WHEN the system is upgraded to support Privy Tier 2 chains.
AND Starknet is added to list of supported networks
THEN Starknet must appear as a selectable network within the Noblocks dashboard and aggregator for supported tokens.
AND a user must be able to initiate and complete Starknet transactions.
Technical details
- Privvy Docs - https://docs.privy.io/recipes/use-tier-2#starknet
- Dependency - https://docs.privy.io/recipes/tee-wallet-migration-guide
Notes/Assumptions
- TEE Migration: The application must migrate to Privy’s Trusted Execution Environment (TEE) architecture, as this is a mandatory prerequisite for Tier 2 chain support.
- SDK Upgrade: All relevant Privy SDKs must be updated to the minimum versions required for TEE and Starknet support.
- Signing Logic: The integration must utilize Privy's "raw signing" capabilities to handle Starknet’s non-EVM transaction format.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request