feat(tempo): multisig #5029
+11,084
−3,051
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| --- | ||
| "viem": patch | ||
| --- | ||
|
|
||
| `viem/tempo`: Added persistent multisig operation coordination and explicit owner approval actions. | ||
|
|
||
| ```ts | ||
|
There was a problem hiding this comment.
The changeset continues after its past-tense summary with a fenced usage example, even though repository changeset entries must consist of a single sentence. Remove the example and retain only the summary sentence. AGENTS.md reference: AGENTS.md:L224-L227 Useful? React with 👍 / 👎. |
||
| import { Multisig, createClient, http } from 'viem/tempo' | ||
|
|
||
| const client = createClient({ | ||
| multisig: { store: Multisig.Store.memory() }, | ||
| transport: http(), | ||
| }) | ||
|
|
||
| const operation = await client.multisig.approveTransaction({ | ||
| ...request, | ||
| account: owner, | ||
| }) | ||
| ``` | ||
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
storageoption in this patchThis changeset declares a patch release even though the commit removes
storagefrom bothsignAuthorizationTokenand the Zonehttptransport. Existing JavaScript callers that prepopulate a custom store and passhttp(..., { storage })will have that option silently ignored, so the authorization token is read from the empty default store and authenticated requests fail; retainstorageas a deprecated alias or ship and document the rename as a major migration.AGENTS.md reference: AGENTS.md:L224-L227
Useful? React with 👍 / 👎.