Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Neat. I'm at a crypto conference in a couple weeks, I'll see if there's any sparks on this idea.

I agree with an above post that the starting point is that you get paid to review, and you pay to get reviewed; although you'd need another way to monetize the token or it's limited to this use case.

The overlap with open-source seem clear: How do you validate the value of the crowd-sourced contributions? In code, you could do it via TDD...

OH! OR - (well, you could make both), you pay to review by _betting for it's validity_. There may be a way to combine or borrow from each approach to fill in the gaps in the other.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: