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
In order to solve issue 14 from kanbanGo, you need to create a withdrawal request for the kanbanGo.
** Please complete point 1 ** in the workflow below. This is the user interface part.
I hereby propose that each withdrawal request be triggered through a submitting a withdrawal transaction. Perhaps the easiest way to design such a transaction would be to make a regular transaction that sends money to address 0xfffff.... or some other distinguished address (another distinguished address you could choose is the address of SCAR or 0x00000... etc.).
Here's a plan for doing this.
[MISSING] Generate a regular kanbanGO transaction sending money from userAddress to 0xffff....
[MISSING] Submit that transaction to kanbanGO
[Should be there out-of-the-box] Mine the transaction (i.e., include it in a kanbanGO block).
[MISSING] After the request is included in a kanbanGO block, trigger the write-back mechanism. The write-back mechanism is the one that is called via the GenerateWriteBackWithdrawal api, however the mechanism must be triggered internally (no api calls necessary).
The text was updated successfully, but these errors were encountered:
In order to solve issue 14 from kanbanGo, you need to create a withdrawal request for the kanbanGo.
** Please complete point 1 ** in the workflow below. This is the user interface part.
I hereby propose that each withdrawal request be triggered through a submitting a withdrawal transaction. Perhaps the easiest way to design such a transaction would be to make a regular transaction that sends money to address 0xfffff.... or some other distinguished address (another distinguished address you could choose is the address of SCAR or 0x00000... etc.).
Here's a plan for doing this.
The text was updated successfully, but these errors were encountered: