You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is an environmental variable for the lock address of each chain supported by Rosen. There is no need for these env vars, because the addresses files from contract repo releases contain not only the lock address, but all other addresses that may be needed in the future.
All of the lock address env vars (which are in the form ofNEXT_PUBLIC_*_LOCK_ADDRESS) should be removed. A new NextJS server action should be introduced (e.g. getNetworkLockAddress), which accepts a network name and returns the lock address for that network (by reading address file contents, etc.). This action can be used in useTransaction hook. Note that there won't be any need for the useLockAddress hook anymore, and it should be removed.
Acceptance conditions
All usages of lock address env vars should be updated based on the provided details (note that intermediary codes probably should be removed, too, such as the lockAddress field in Network objects)
A server action should be added based on the provided details
useLockAddress hook should be removed
.env.example should be updated
The text was updated successfully, but these errors were encountered:
Description
Currently there is an environmental variable for the lock address of each chain supported by Rosen. There is no need for these env vars, because the addresses files from contract repo releases contain not only the lock address, but all other addresses that may be needed in the future.
All of the lock address env vars (which are in the form of
NEXT_PUBLIC_*_LOCK_ADDRESS
) should be removed. A new NextJS server action should be introduced (e.g.getNetworkLockAddress
), which accepts a network name and returns the lock address for that network (by reading address file contents, etc.). This action can be used inuseTransaction
hook. Note that there won't be any need for theuseLockAddress
hook anymore, and it should be removed.Acceptance conditions
lockAddress
field in Network objects)useLockAddress
hook should be removed.env.example
should be updatedThe text was updated successfully, but these errors were encountered: