Draft
Conversation
Add intent URL parsing, resolution, and handling pipeline: Models: - IntentActionItem: SendTon, SendJetton, SendNft action types - IntentRequestEvent: Transaction, SignData, Action intent events - IntentResponse: Transaction, SignData, and error response types - BatchedIntentEvent: Multiple intents in a single event Handlers: - IntentParser: URL parsing, validation, wire-to-model mapping - IntentResolver: Action items to TransactionRequest conversion, action URL fetching with jetton/NFT message building - IntentHandler: Orchestrator with parse-resolve-emulate-emit flow, approval/rejection methods, pending connect request management Integration: - TonWalletKit: 10 public intent API methods - BridgeManager: sendIntentResponse with ephemeral SessionCrypto - Android bridge: Full intent API surface with event listeners
1. Action URL response parsing: handle { action_type, action } format
per spec instead of wire intent format. sendTransaction actions
return standard messages array, signData returns typed payload.
2. Query param: use 'address' instead of 'wallet' when appending
wallet address to action URL (spec requirement).
3. Wire response format: convert SDK response models to spec format
before sending via bridge:
- txIntent/signMsg: { result: '<boc>', id }
- signIntent: { result: { signature, address, timestamp, domain, payload }, id }
- error: { error: { code, message }, id }
4. SignData response: add echoed payload field per spec requirement
(MakeSignDataIntentResponseSuccess = SignDataResponseSuccess).
… multi-item intents
…e error messaging
…ning and adjust related logic in IntentHandler
…gy, add validation for missing actionUrl
…-371-demo-wallet-intents
…-371-demo-wallet-intents
…-371-demo-wallet-intents # Conflicts: # apps/demo-wallet/src/pages/WalletDashboard.tsx # demo/wallet-core/src/hooks/useWalletStore.ts # demo/wallet-core/src/index.ts # demo/wallet-core/src/store/createWalletStore.ts # demo/wallet-core/src/types/store.ts # pnpm-lock.yaml
…-371-demo-wallet-intents
…nts in WalletDashboard
…-371-demo-wallet-intents
…-371-demo-wallet-intents
…-371-demo-wallet-intents
…-371-demo-wallet-intents
…-371-demo-wallet-intents
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
||
| export type StructuredItemType = 'ton' | 'jetton' | 'nft'; | ||
|
|
||
| export type StructuredItem = TonTransferItem | JettonTransferItem | NftTransferItem; |
| amount: string; | ||
| payload?: string; | ||
| stateInit?: string; | ||
| extraCurrency?: { [k: number]: string }; |
| address: string; | ||
| amount: string; | ||
| payload?: string; | ||
| stateInit?: string; |
Contributor
There was a problem hiding this comment.
@TrueCarry Specify correct types for all fields - this related to all models in this files
| export type StructuredItem = TonTransferItem | JettonTransferItem | NftTransferItem; | ||
|
|
||
| /** Snake_case wire-format items as received in JSON-RPC payload */ | ||
| export type RawStructuredItem = RawTonTransferItem | RawJettonTransferItem | RawNftTransferItem; |
Contributor
There was a problem hiding this comment.
@TrueCarry I'm not sure that we need raw types in models
|
|
||
| // --- Conversion helpers --- | ||
|
|
||
| export function parseRawStructuredItem(raw: RawStructuredItem): StructuredItem { |
Contributor
There was a problem hiding this comment.
@TrueCarry Remove functions from models layer completely
| const hasValueWrapper = type.getTypes().every((variant) => this.getAssociatedValueType(variant) !== null); | ||
| if (!hasValueWrapper) { | ||
| return false; | ||
| } |
Contributor
There was a problem hiding this comment.
@TrueCarry Lets remove this, will add different logic if needed
| async getSignedSendTransaction( | ||
| input: TransactionRequest, | ||
| _options: { fakeSignature: boolean }, | ||
| options?: { fakeSignature?: boolean; internal?: boolean }, |
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
3 participants
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.
No description provided.