Viewing a response to: @brianoflondon/re-1681900525235
I mean I totally see the use case buuut it's a bit tricky to implement so idk if it's worth it
| author | howo |
|---|---|
| permlink | re-brianoflondon-rtfomg |
| category | documentation |
| json_metadata | {"tags":["documentation"],"app":"peakd/2023.4.2"} |
| created | 2023-04-20 21:49:36 |
| last_update | 2023-04-20 21:49:36 |
| depth | 4 |
| children | 1 |
| last_payout | 2023-04-27 21:49:36 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 95 |
| author_reputation | 515,737,941,459,006 |
| root_title | "Recurrent transfer documentation" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 122,746,141 |
| net_rshares | 0 |
Not wanting to flog this too far but something akin to the CRON interface would cover everything. Perhaps that's not impossible to implement? I do understand that whatever code is used has to run in the core of Hive and be extremely performant. Anyway I don't see a lot of usage of recurrent transfers yet so we should keep an eye on this if my use case starts to get traction.
| author | brianoflondon |
|---|---|
| permlink | re-howo-rtgrgj |
| category | documentation |
| json_metadata | {"tags":["documentation"],"app":"peakd/2023.4.2"} |
| created | 2023-04-21 11:48:21 |
| last_update | 2023-04-21 11:48:21 |
| depth | 5 |
| children | 0 |
| last_payout | 2023-04-28 11:48:21 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 381 |
| author_reputation | 760,655,352,092,696 |
| root_title | "Recurrent transfer documentation" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 122,762,177 |
| net_rshares | 0 |
hiveblocks