Closed 0x4007 closed 1 year ago
Deadline | Thu, 31 Aug 2023 13:55:27 UTC |
Registered Wallet | 0x16B2433b9CF5FF87dE03dDaEea627C9106Ee117a |
/wallet 0x0000...0000
if you want to update your registered payment wallet address @user.@pavlovcik As previously mentioned I filled out the Paymentology questionnaire in a file available only for Ubiquity team members. Submission of the questionnaire in the form of a publicly available PR should not be done because of the NDA.
Please review the content so I can submit it to Paymentology. If you need to change something, please write a comment to the document.
@sergfeldman - Releasing the bounty back to dev pool because the allocated duration already ended! Last activity time: Wed Aug 30 2023 13:56:26 GMT+0000 (Coordinated Universal Time)
I just checked the document and left a comment on what you should do. This shouldn't take more than 10 minutes to do.
Permit generation skipped because the issue was not closed as completed
Permit generation skipped since this issue didn't qualify as bounty
@pavlovcik The bounty for Paymentology was artificially divided into 3 tasks. The essence of this task is not only filling out the Projections table, but 1/3 of the entire task for Paymentology. You can double-check the division in the comments https://github.com/ubiquity/card-issuance/issues/12
As I see, you removed the Price label from this task, which means I will not receive payment for it. From the point of view of a bounty hunter, it looks like after completing a task, the DevPool reduces the total payment from the amount that was determined at the beginning of the task.
Please clarify your position on this matter.
/allow set-time @sergfeldman true
Updated access for @sergfeldman successfully! Access: time for "ubiquity/card-issuance"
/query @sergfeldman
@sergfeldman's wallet address is 0x16B2433b9CF5FF87dE03dDaEea627C9106Ee117a, multiplier is 1 and access levels are
access type | access level |
---|---|
multiplier | false |
priority | false |
time | true |
price | false |
https://gnosisscan.io/tx/0xf295a5eaba7e03274cd3eed059b8ebb3f3dc4bc8639ed8175bf14675e853402f
This was during the conference so I had basically zero time to look into this. It's my fault for not actually checking the scope of work before approving the budget.
@pavlovcik Thank you for the payment!
I don't think there is somebody's fault because it is hard to estimate such tasks beforehand. Filling out this questionnaire for Paymentology has already taken 2 times longer due to unplanned research of BIN sponsors, and it will take even more time. After the meeting with Paynentology next week I will probably have to change the answers to some questions.
/start