https://github.com/halseth/elftrace

https://github.com/halseth/elftrace

Last synced: 18 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/halseth/elftrace
• Owner: halseth
• Created: 2023-11-17T14:06:13.000Z (12 months ago)
• Default Branch: main
• Last Pushed: 2024-09-24T17:51:39.000Z (about 2 months ago)
• Last Synced: 2024-10-14T09:47:40.389Z (about 1 month ago)
• Language: Rust
• Size: 1.31 MB
• Stars: 32
• Watchers: 4
• Forks: 7
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• awesome-bitvm - Elftrace

README

        
# Bitcoin Elftrace

Verify RISC-V binary execution in Bitcoin script.

## What is this?

`Bitcoin Elftrace` is a proof of concept tool used to trace the execution of

RISCV-32 binaries (ELFs), and generate Bitcoin script that can be used to

verify this execution on-chain.

## How do I use it?

See the [compilation doc](./docs/compile.md) for an example of how to trace a

RISC-V binary, or the [ZK verification example](./docs/zk_verifier.md) for how

to write a STARK verifier in Rust that can be traced.

## What is this useful for?

Using this you can use your favourite language to write arbitrary programs that

can be verified on Bitcoin. Paired with the "optimistic execution" smart

contracting paradigm, this opens up the possibility for Bitcoin smart contracts

to be arbitrary complex while still keeping the on-chain footprint low.

## What is optimistic execution?

The idea is to write your UTXO smart contracts in a way that gives any spender

the incentive to act honestly. If someone tries to spend the UTXO with an

improper execution of the contract, they can be punished efficiently using a

fraud proof.

## How can I use elftrace to write Bitcoin smart contracts?

`elftrace` only (currently) generates the scripts needed to validate the

program execution. You will need to wrap the program in a "MATT challenge"

style script in order to set up a proper smart contract. See

[mattlab](https://github.com/halseth/mattlab/blob/main/docs/challenge.md) for

an example.

## Are there any limitations?

This is very much in a POC stage. Here's a non-exhaustive list of known

issues/TODOs:

- [ ] `CScriptNum` is used when doing operations on address locations and

  various other operations. This can fail if numbers exceed 31-bit.

- [ ] RISC-V opcodes `SLTI`, `LB`, `SLT`, `SRA` currently not implemented.

## When can I use this on mainnet?

In order to use this on mainnet we would need to deploy a _covenant opcode_.

`elftrace` is based on the `OP_CHECKCONTRACTVERIFY` opcode proposed by

[MATT](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-November/021182.html).

Come join us in getting covenants deployed on Bitcoin! 🤠

## What does this enable on Bitcoin?

Having a covenant deployed on bitcoin would enable us to use this to create

trustless two-way pegs, rollups, ZK verifiers... in general much more

flexible ways of handing custody of coins to an on-chain computer program.