Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update migration portfolio to include shared objects #4805

Open
begonaalvarezd opened this issue Jan 15, 2025 · 0 comments · May be fixed by #4974
Open

Update migration portfolio to include shared objects #4805

begonaalvarezd opened this issue Jan 15, 2025 · 0 comments · May be fixed by #4974
Assignees
Labels
tooling Issues related to the Tooling team wallet-dashboard Issues related to the Wallet Dashboard dApp
Milestone

Comments

@begonaalvarezd
Copy link
Member

begonaalvarezd commented Jan 15, 2025

Fetch shared objects from the custom indexer (configured in an .env & fetch only if provided) and update migration portfolio to include these new objects (no need to proceed with the migration yet)
Note to use the indexer endpoint that already resolves the expiration owner to avoid doing extra logic on our side

Depends on https://github.com/iotaledger/tooling-resources/issues/62

@begonaalvarezd begonaalvarezd added the tooling Issues related to the Tooling team label Jan 15, 2025
@begonaalvarezd begonaalvarezd added this to the Mainnet milestone Jan 15, 2025
@begonaalvarezd begonaalvarezd changed the title Update migration portfolio to include shared objects too Update migration portfolio to include shared objects Jan 15, 2025
@begonaalvarezd begonaalvarezd added the wallet-dashboard Issues related to the Wallet Dashboard dApp label Jan 15, 2025
@begonaalvarezd begonaalvarezd marked this as a duplicate of #3789 Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tooling Issues related to the Tooling team wallet-dashboard Issues related to the Wallet Dashboard dApp
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants