# 1.1. Motivation

The idea of smart contracts, originating from Nick Szabo, remains an inspiration for an almost a generation of innovators. However its promises to become a foundation for technically-guaranteed agorism, anarcho-capitalism and cryptoanarchism were never fulfilled - since all l existing systems claiming to be “smart contract platforms” so far fail to deliver required properties of the smart contract trilemma:

1. Be scalable
2. Has sufficient programmability (be nearly-equivalent to a universal Turing machine)
3. Be decentralized and censorship-resistant

The last decade the joint work of a number of cryptographic researches and cypherpunk thinkers has brought a new foundations which can be utilized in achieving the goal. This includes concepts of client-side-validation and single-use-seals by Peter Todd and client-validated “colored coins” of Giacomo Zucco able to operate as a scalable layer on top of bitcoin and lightning network. In this proposal we merge this ideas with prominent privacy-preserving tech (confidential transactions by Blockstream, enhanced with Bulletproofs++ range proofs) and novel concepts of partially-replicated state machines, functional confined type system and registry-based virtual machine developed by me in UBIDECO Institute to create a new programmable, secure, privacy-preserving, censorship-resistant and scalable smart contract system called RGB.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://black-paper.rgb.tech/general-information/1.-introduction/1.1.-motivation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
