Tags: cycorld/sui
Tags
Gas budget in SUI (MystenLabs#8676) ## Description Change Gas Budget to be in sui rather then gas units, that removes the concept of gas units from any user related API. Internally we move to gas units as soon as we make `SuiGasStatus` so the change is very minimal. The format of the `TransactionData` is not changed (`u64`), so effectively this is not a breaking change as a format but it requires clients to think about how they use gas budget. Most of our codebase (tests) use a gas price of 1 (DUMMY_GAS_PRICE), so GAS UNITS or MIST are the same, which explains why almost nothing broke. Locally I changed the DUMMY_GAS_PRICE to be 2 and some tests broke, however I verified that they were all using constants that had to be changed. So this seems to be really the only change needed. Tests pass so we are good. I need to produce documentation about this change - and others I have - but given we are not going out with this in devnet, that can wait a day or two (doing it as soon as I move all blockers from my plate). @Jordan-Mysten @gegaowp @patrickkuo @666lcz please let me know if you see issues or we can move this forward ## Test Plan Existing test --- If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process. ### Type of Change (Check all that apply) - [ ] user-visible impact - [ ] breaking change for a client SDKs - [ ] breaking change for FNs (FN binary must upgrade) - [ ] breaking change for validators or node operators (must upgrade binaries) - [ ] breaking change for on-chain data layout - [ ] necessitate either a data wipe or data migration ### Release notes
Adding new Exchange Integration Guide (MystenLabs#8721) ## Description Added a new Exchange Integration Guide, merged in the FAQ into this topic. ## Test Plan Manual tech review and staging server --- If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process. ### Type of Change (Check all that apply) - [x] user-visible impact - [ ] breaking change for a client SDKs - [ ] breaking change for FNs (FN binary must upgrade) - [ ] breaking change for validators or node operators (must upgrade binaries) - [ ] breaking change for on-chain data layout - [ ] necessitate either a data wipe or data migration ### Release notes Adds a new topic, Sui Exchange Integration Guide
Remove bulletproofs and EC operations from Move (MystenLabs#8660) ## Description Removing bulletproofs and EC operations from Move. These require major audit and once it is done we will add them back to Move. ## Test Plan All tests pass. ### Type of Change (Check all that apply) - [ ] user-visible impact - [ ] breaking change for a client SDKs - [x] breaking change for FNs (FN binary must upgrade) - [x] breaking change for validators or node operators (must upgrade binaries) - [x] breaking change for on-chain data layout - [ ] necessitate either a data wipe or data migration ### Release notes Removing bulletproofs and EC operations from Move. These require major audit and once it is done we will add them back to Move.
Remove SignatureSeed (not in use) (MystenLabs#8657) ## Description Remove `SignatureSeed` (not in use). ## Test Plan All tests pass.
[wallet-kit] Add support for `signMessage` (MystenLabs#8690)
genesis: initialize the subsidy fund and transfer remaining sui to du… …mmy account
wallet-ext: check all accounts before importing a private key (Mysten… …Labs#8620) ## Description * avoid importing an account that already exists in the wallet and is already derived from the mnemonic * for the case we import a keyPair and then derive an account from the mnemonic that is the same handle the account as a derived one https://user-images.githubusercontent.com/10210143/221228772-3e1bb7d4-b68a-41f8-ac32-0845efff3cae.mov ## Test Plan * export an existing derived account * try to import it closes APPS-534
unblock request_set_commission_rate function (MystenLabs#8656) ## Description We blocked calls to `request_set_commission_rate` only for testnet wave 2. Now we should unblock it. After this removal there is no more blocked functions but the logic is kept there in case we want to use it again in the future. ## Test Plan How did you test the new or updated feature? cargo test --- If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process. ### Type of Change (Check all that apply) - [ ] user-visible impact - [ ] breaking change for a client SDKs - [ ] breaking change for FNs (FN binary must upgrade) - [ ] breaking change for validators or node operators (must upgrade binaries) - [ ] breaking change for on-chain data layout - [ ] necessitate either a data wipe or data migration ### Release notes
[move] Expose epoch timestamp through `TxContext` (MystenLabs#8627) ## Description This allows even single-owner transactions to have access to a concept of time that ticks with each epoch change. ## Test Plan ``` cargo nextest run ``` + New test for the test scenario changes: ``` cargo nextest run -- 'run_framework_move_unit_tests' ``` ### Type of Change (Check all that apply) - [x] user-visible impact - [ ] breaking change for a client SDKs - [x] breaking change for FNs (FN binary must upgrade) - [x] breaking change for validators or node operators (must upgrade binaries) - [ ] breaking change for on-chain data layout - [ ] necessitate either a data wipe or data migration ### Release notes Expose the start timestamp of the epoch that the transaction is running in via the `TxContext`, using `sui::tx_context::epoch_timestamp(ctx: &TxContext): u64`. This concept of time is available even for single-owner transactions.
PreviousNext