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
I think the tools/hashLockCondition.js script made to illustrate adding spending condition (SC) really helps newcomers to Leap (like me!) to work with the concept. All I have to do in order to deploy and test SC is write proper solidity and run the script.
In my opininon it might be worthwile to create a more generalized script that takes arguments in form: deploy.js <condition_name> and then 1) deploys SC of a given <condition_name> to RPC_URL 2) waits for a transaction to see what SC does once it gets some tokens just like your tool.
Since different spending conditions have different parameters (e.g. address constant tokenAddr = 0x1111111111111111111111111111111111111111;) I think it is the developer that should set those on compile time, rather then ninja-editing it like hashLockCondition.js does, but both approaches have its merit.
EDIT: Closed in favor of #15 which takes the proposal further and is much better specified.
The text was updated successfully, but these errors were encountered:
I think the
tools/hashLockCondition.js
script made to illustrate adding spending condition (SC) really helps newcomers to Leap (like me!) to work with the concept. All I have to do in order to deploy and test SC is write proper solidity and run the script.In my opininon it might be worthwile to create a more generalized script that takes arguments in form:
deploy.js <condition_name>
and then 1) deploys SC of a given<condition_name>
to RPC_URL 2) waits for a transaction to see what SC does once it gets some tokens just like your tool.Since different spending conditions have different parameters (e.g.
address constant tokenAddr = 0x1111111111111111111111111111111111111111;
) I think it is the developer that should set those on compile time, rather then ninja-editing it likehashLockCondition.js
does, but both approaches have its merit.EDIT: Closed in favor of #15 which takes the proposal further and is much better specified.
The text was updated successfully, but these errors were encountered: