-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Add support for sign_transfer * docs(changeset): Support sign_transfer for NEAR * Support sign transfer * Cleanup * Remove this * Remove this * Update README * README cleanup * Update changelog * Formatting
- Loading branch information
Showing
9 changed files
with
189 additions
and
19 deletions.
There are no files selected for viewing
This file contains 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,22 @@ | ||
--- | ||
"omni-bridge-sdk": minor | ||
--- | ||
|
||
feat(near): Implement end-to-end transfer signing flow | ||
|
||
### Added | ||
|
||
- `signTransfer` method in NearBridgeClient to authorize transfers after initialization | ||
- New event types (`InitTransferEvent`, `SignTransferEvent`) for tracking NEAR transfer lifecycle | ||
- Automatic storage deposit handling for token contracts interacting with the locker | ||
|
||
### Changed | ||
|
||
- `initTransfer` on NEAR now returns structured event data instead of raw tx hash | ||
- Updated transfer flow documentation with NEAR-specific examples | ||
- Unified BigInt handling across EVM/Solana clients for consistency | ||
|
||
### Breaking Changes | ||
|
||
- NEAR `initTransfer` return type changed from `string` to `InitTransferEvent` | ||
- NEAR transfers now require explicit `signTransfer` call after initialization |
This file contains 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 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 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 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 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 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 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 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