Skip to content

Conversation

@valeriyr
Copy link
Contributor

@valeriyr valeriyr commented Oct 7, 2025

Description of change

IOTAccount is used in the dynamic_multisig_account example.

@valeriyr valeriyr self-assigned this Oct 7, 2025
@vercel
Copy link

vercel bot commented Oct 7, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

6 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
apps-backend Ignored Ignored Preview Oct 7, 2025 10:47am
apps-ui-kit Ignored Ignored Preview Comment Oct 7, 2025 10:47am
iota-evm-bridge Ignored Ignored Preview Oct 7, 2025 10:47am
iota-multisig-toolkit Ignored Ignored Preview Oct 7, 2025 10:47am
rebased-explorer Ignored Ignored Preview Oct 7, 2025 10:47am
wallet-dashboard Ignored Ignored Preview Comment Oct 7, 2025 10:47am

@iota-ci iota-ci added sc-platform Issues related to the Smart Contract Platform group. vm-language Issues related to the VM & Language Team labels Oct 7, 2025

// Store the transaction.
self.transactions_mut().add(transaction_digest, member_address);
transactions_mut(self, ctx).add(transaction_digest, member_address);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A transaction can be proposed by any account's member. In the current IOTAccount implementation, it is impossible; we can borrow mutable dynamic fields only when the sender is the account itself.

Base automatically changed from vm-lang/aa-auth/8754-reimplement-auth-info-df-name to vm-lang/aa-auth/8116-feature-branch October 8, 2025 07:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

sc-platform Issues related to the Smart Contract Platform group. vm-language Issues related to the VM & Language Team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants