The main idea around object capabilities, decades before cryptocurrencies and all that, was around the idea of so-called "smart contracts", which really boils down to "Code that does financial and legal things on our behalf", and the core takeaway from that was that if you don't have a serious computer security model, there's no real way to do this right.When I say serious computer security model, for non-tech folks, I don't mean "Install the latest virus scanner.", I mean you need complete assurance that a program that's meant to do one thing can't do something else- not "should not" or "won't try", I mean "can't", as in even if the person who wrote this program is pure evil, the thing they want to do won't happen.And the best way we know how to do that is the object capabilities model. It's not the only way, but we've learned in the last ~35 years that it's the only practical way.Now let's talk about AI and LLMs...1/#Programming #AI #OCAP #Capabilities #Agents #SmartContracts

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 1 point 1 year ago (1 child)

@peribotsarah Nothing so complex! These systems pre-date blockchains by decades.In its most primitive form, OCAP simply means that capabilities are expressed as unforgable addresses in a system.A file descriptor in a Unix system is an example of one, as is a password reset token. A password reset token can only be used for password reset on one account. It can't be used to do other things. A file descriptor lets you do things to one file, not any file you want, etc.Imagine if you handed a malicious program a read only file descriptor to a file. It might want to write to it, but if all it had was just the file descriptor and nothing else, it wouldn't be able to do anything.

  • source
  • parent
  • hideshow 1 child comment