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

Tracking issue for v13 #475

Closed
9 tasks done
Reecepbcups opened this issue Jan 4, 2023 · 5 comments
Closed
9 tasks done

Tracking issue for v13 #475

Reecepbcups opened this issue Jan 4, 2023 · 5 comments
Labels
tracking issue This is used to track a more complicated piece of work that might have multiple dependencies

Comments

@Reecepbcups
Copy link
Contributor

Reecepbcups commented Jan 4, 2023

@Reecepbcups Reecepbcups added the tracking issue This is used to track a more complicated piece of work that might have multiple dependencies label Jan 4, 2023
@faddat
Copy link
Contributor

faddat commented Jan 10, 2023

I disagree about IBC test, and think it should be removed from the v13 roadmap.

However if we're able to do it with a reasonable level of effort, great. There does seem to be one flaky test. The thing is I'm not sure that IBC test is going to fix the flaky test either.

@faddat faddat mentioned this issue Jan 10, 2023
2 tasks
@the-frey
Copy link
Collaborator

the-frey commented Feb 6, 2023

2023-02-06 update after dev call

Current slated v13 has diverged, as we are doing version bumps for v12, and splitting the "old" v12 into two, v13 and v14 of Juno.

The plan for v13 now is:

  • Packet Forward Middleware
  • Feeshare
  • Token Factory
  • Remove intertx

Further discussion needed on 0.30 of wasmd if available because of IBC fees & IBC v4, i.e these are

  • IBC v4
  • 0.30 wasmd
  • Token Factory -> IBC v4
  • IBC Fee

Looking forward to v14, we also expect to get in

@nicolaslara
Copy link
Contributor

IBC hooks (from Osmosis, but these need permissioning)

IIUC, the wasmkeeper.NewDefaultPermissionKeeper defaults to permissionless. It checks the params to see who is authorised to upload/instantiate, and the default is "Everybody":

junod q wasm params --node https://rpc.juno.kingnodes.com:443

code_upload_access:
  address: ""
  addresses: []
  permission: Everybody
instantiate_default_permission: Everybody

Am I missing something @the-frey ?

@Reecepbcups
Copy link
Contributor Author

@nicolaslara We are going to prioritize this for v14, will keep you updated

@Reecepbcups
Copy link
Contributor Author

Successful launch 🥳 Onto v14 now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tracking issue This is used to track a more complicated piece of work that might have multiple dependencies
Projects
None yet
Development

No branches or pull requests

4 participants