About me

Just show up anytime jobs

Recently there was the second weekly Ethereum video hangout. Casey Kuhlman made a good recap.

However, the way roles were talked about seemed to imply more fixedness than many DAOs might have for their business model. Since there is a cost to hiring people, many sorts of DAOs may just use spontaneous contributions as ‘labour’ input, where the DAO does not put in requirements for participation. This could be the case when:

Below are some examples, really, each of them is an entire topic on itself. Even though this post got a bit too long, it does not nearly cover the entire idea. Note that i am not sure on the feasibility of these, not in the near term, anyway.

Opportune: Rideshares, ‘Mechanical Turk’

Taking people and stuff along with you to places near the route you are going anyway already, where time is not critical but location is. Estimating ability to carry and, using some sort or reputation and/or stake system is needed.

Could really imagine anything, like sweeping the streets, but with package delivery, the signal wether things went well is stronger.

The ‘Mechanical Turk’ is the opposite, largely here time may be critical, but location isnt, so if you can attract enough people you can serve them.

Publishing DAO’s

You can timestamp documents by publishing their checksum on the blockchain. (cryptographic commitment) Chronos does this, for instance.

However, a way could be determined to indicate the ‘derivativeness’ of two timestamped documents, Different contexts may have different ways of determining ‘derivativeness’.

Income is a separate problem, for instance a publish DAO could use DHT methods to prove it is showing advertisements, advertisers ask to buy the spots, and the highest paying get them. Authors would have be able to vote on whether advertisements are abusive. Another source of income could be donations.

Approaches using DHT may not entirely neccessary Advertisers could simply ‘patrol’ the pages and value the according to how consistently ads are placed.

In the context of package repositories, an idea i heard from Casey Kuhlmann was that you can use the combination of name registries that help hold on to a name, loyalty between open source developpers to credit their dependencies to create a system where donations are passed along.

Using stake: RANDAO

Dennis McKinnon’s RANDAO. is a random value(seed) generator for other contracts. Future block hashes are random for this purpose, but can be affected by miners colluding with betters.(failing to report blocks, because the bets earn more)

In essence it works by various parties using a cryptographic commitment -the hash of a random value- and then in the second stage the same party releases the random value. Random values are then combined so none of the parties can determine it onesidedly. In essence, any party can just come in and play along.

Of course, parties can still fail to report the random value if the, or people they deal have bets that may swing in that case. Which is the equivalent of not reporting blocks in the case of future blocks. However as here it is a contract, the stake can be a lot bigger than a single block reward.

Where to send the money

DAOs dont have top-salaries to pay or dividents to pay, at least, a good one at worst only pays dividents up to an amount paying back for investment. I am critical of dividents of corporations, but DAOs really dont have investments to make, unless they’re really clever and can use it to program new things..

They have to do something with their earnings, if they have a margin. Accumulating is sort-of a waste for the community using and putting effort in it. As far as i can tell, are three ways to go, none excluding the others, and what to do is context sensitive.

  1. Cheapen their service, eliminating the margin.

  2. Goes to the contributors.

  3. Goes to some other (decentralized)organization, for instance human-identification system with UBI. Possibly could be an organization that is based on contributors to the system itself too.

This passes responsibilities on. I.e. there is the question how well you could trust that organization.(or insofar it doesnt require trust)

However, it could deal with social problems that are not solved by figuring out some business model.

For rideshares, different approaches of rideshares will compete, so it will tend to go to 1 and 2 as transporters and consumers seek cheapness. Of course what that will be depends on what other opertunities transporters have.

The Publication DAO, might have fans, and something like Wikipedia DAO might have quite a bit of network effects. Since i dont have that much respect for the idea of advertising, and the method to trustlessly choose who gets the spots, i am of the opinion that it should do 2/3.

With RANDAO, i reckon (1) is the best way to go by far. Other contracts depend on it, and it doesnt involve many people directly.

Added note, for the record, this is all open to discussion, of course!

Blog Posts

2021-07-17 Type Stack Calculation project intro
2020-08-26 Camcorder planet viewing
2020-05-15 I Made a Sha256 based port knocking program
2017-12-26 Probably kindah like a Snowflake simulation
2017-10-29 More Pixel fun turtles
2016-09-22 Pixel fun - messing with turtles
2016-05-17 Finally put together page_html
2015-11-12 libre decentralized software
2015-02-03 Tinfoilchat inspired ideas
2015-01-07 Public goods and business models
2014-12-22 Captcha Quicky
2014-12-12 Assurance contract mention
2014-11-21 Publishing DAO, and its holy grail
2014-11-02 Grudge escrow contract
2014-09-11 The core Blockchain idea
2014-06-03 Hanging blocks
2014-05-29 Voting power needed for DAO/DO decisions
2014-05-17 What is Ethereum to people?
2014-05-08 Just show up anytime jobs
2014-05-08 Proof of Reserve and voting
2014-05-08 DHTs: more than just storage