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.

Sign up for GitHub

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

Jump to bottom

docs: add changelog entry for v0.34.0 upgrade #1948

Merged
merged 1 commit into from
May 1, 2024
Merged

docs: add changelog entry for v0.34.0 upgrade #1948

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions upgrades/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,21 @@ Goal of the upgrade here
Add new upgrades after this line based on the template above
-----

##### v0.34.0

1. Extend authz implementation for DeploymentDeposit to allow grantee re-use of unspent funds.
- Example of previous behavior:
Deployment authz granted from account B (grantor) to account A (grantee) in amount of 5AKT.
Deployment is created with authorized spend and deposit amount of 3AKT.
Deployment spends 1.5AKT and lease was closed. 1.5AKT remainder is returned to the grantor, and authorization has 2AKT left to spend
- Example of new behavior:
Deployment authz granted from account B (grantor) to account A (grantee) in amount of 5AKT.
Deployment is created with authorized spend and deposit amount of 3AKT.Deployment spends 1.5AKT and lease was closed.
1.5AKT remainder is returned to the grantor, and authorization is updated and has 3.5AKT left to spend.
2. Don’t allow multiple grants from different grantors to be used for deposit on same deployment.
This issue may lead to a case where all remaining funds after deployment is closed are returned to last grantor.
Such use case has been guarded against and only one authz depositor will be allowed per deployment

##### v0.32.0

1. remove checking if provider has active leases during provider update transactions. This check was iterating thru all existing leases on the network causing gas and thus transaction fees go to up to 3AKT which is way above desired values. Initial intention of check was to prevent provider changing attributes that is in use by active leases. Akash Network team will reintroduce check by adding secondary indexes in future network upgrades.
Expand Down
Loading