3 ms·
> 2. Allocating bandwidth, storage, compute. Before Bitcoin was a thing, I was thinking about the Erlang VM's "reduction-counting" processing paradigm, and not
by derefr 12y ago
> 2. Allocating bandwidth, storage, compute.
Before Bitcoin was a thing, I was thinking about the Erlang VM's "reduction-counting" processing paradigm, and noticed that it was a lot like having a dom0-scheduler "treasury" with domU-process "citizens", where each citizen gets paid a basic income every scheduling interval, and then can spend it to "purchase" time-spent-aware on a virtual core.
In Erlang's model, processes lose whatever they don't spend in a given interval—this is necessary to prevent a process from "saving up" and then blocking the VM for seconds at a time. However, if rather than putting a cap on wealth, you just cap spending per interval, then processes could do lots of other clever things with their income: trade it, invest it, spawn subagents that consume it, etc. This would be a very interesting platform for running goal-directed AI agents on: somewhere between Core Wars and Heroku.
Now, if the only "ledger" of reductions was in the local dom0, you'd have nothing more than a toy server: a sort of fishtank for agents to interact within. But throw a blockchain at the problem, and now agents could pay to spawn sub-agents (or copy themselves) anywhere that'll take their dom0's currency.
Interestingly, since cryptocoins are all pretty fungible, this would imply that the "intelligence" of an AI—or of a hypothetical Hansonian brain-emulation, for that matter—could be measured in units of dollars-spent-per-second.
- abecedarius 12y agoSee http://e-drexler.com/d/09/00/AgoricsPapers/agoricpapers.html http://e-drexler.com/d/09/00/AgoricsPapers/agoricpapers.html for more in that line. Also http://www.cap-lore.com/Economics/DSR/ http://www.cap-lore.com/Economics/DSR/ and http://www.whatisthought.com/eric.html http://www.whatisthought.com/eric.html under "artificial economies of agents that reinforcement learn".
- lpgauth 12y agoCool idea, the only problem I can see is how you define a reduction. In the Erlang VM a reduction is kind of a magical unit... and not a reductions are created equal.
- derefr 12y agoI think the definition of a reduction (in terms of what it buys) is allowed to be pretty much arbitrary while still having an effective distributed economy emerge on top of it. Think of it as a communist state that both issues currency, and sets arbitrary prices for all state-produced goods in terms of that currency. In one state, a loaf of bread (or a multiplication) might be worth $1, and a hamburger (or a network message send) $5; in another state, the costs might be reversed. This would shake out as 1. exchange rate nash-equilibria between dom0s, determined by their "monetary policies"; and 2. spawning of subagents on dom0s with better cost-structures for the particular tasks they're assigned to accomplish. (If you're doing a lot of network IO, you'd want to delegate that part of your job to a place where network IO—after currency-conversion—is cheap.)
- lpgauth 12y agoRight, if reductions are market based then yes, it would work.