Super useful.. thank you! I've got the daily funding logic in place now

Excellent! You have the best way of visualizing worker proposals in the whole world as of now, literally.If you want to improve the display, here are some other hints:1) Worker objects never expire. Also some workers are not valid yet. You probably should filter out your worker list to only show active and valid ones.2) However, it is important that upcoming proposals get visibility. Perhaps a separate table of "pending proposals" ranked in order of votes for proposals which have not started yet.

1) I thought work_end_date was the expiration date, and a worker will be paid daily for the period of work_begin_date --> work_end_date, no?2) For now I've distinguished active/upcoming using colors.. when we have a few more workers and funding starts to be limited I'll add a better indicator of active vs unfunded vs upcoming

Super useful.. thank you! I've got the daily funding logic in place now

Excellent! You have the best way of visualizing worker proposals in the whole world as of now, literally.If you want to improve the display, here are some other hints:1) Worker objects never expire. Also some workers are not valid yet. You probably should filter out your worker list to only show active and valid ones.2) However, it is important that upcoming proposals get visibility. Perhaps a separate table of "pending proposals" ranked in order of votes for proposals which have not started yet.

1) I thought work_end_date was the expiration date, and a worker will be paid daily for the period of work_begin_date --> work_end_date, no?2) For now I've distinguished active/upcoming using colors.. when we have a few more workers and funding starts to be limited I'll add a better indicator of active vs unfunded vs upcoming

Thanks!1) Yes, but I think the object remains in memory, just is NULL (I could be wrong) -- I guess we'll see in a few days!2) great!