Welcome to BuilderNet

Documentation

• buildernet.org/docs/send-orderflow
• buildernet.org, forum

Sending Orderflow to BuilderNet

curl https://_BUILDERNET_INSTANCE_ \
    --header 'Content-Type: application/json' \
    --header 'X-Flashbots-Signature: _public_key_address_:_signature_' \
    --data '{
        "id": 1,
        "jsonrpc": "2.0",
        "method": "eth_sendBundle",
        "params": [{
            "blockNumber": "0x1361bd3",
            "txs": [
                "0x100000...",
                "0x200000..."
            ]
        }]
    }'

You can use the --cacert builder-cert.pem option with curl to verify the attested TLS certificate of the BuilderNet node.

See also the full documentation at

• buildernet.org/docs/api
• buildernet.org/docs/send-orderflow

TEE Proof Validation

You can retrieve the certificate over a TEE-attested channel, verifying the identity of the server, and then use it to verify the TLS connection:

# Install attested-get tool
git clone https://github.com/flashbots/attested-tls-proxy.git
cd attested-tls-proxy
curl -fSsL https://measurements.buildernet.org > /tmp/measurements-buildernet.json

cargo run -- attested-get \
  --measurements-file /tmp/measurements-buildernet.json \
  https://_BUILDERNET_INSTANCE_:7936

See more details about attested-get in the attested-tls-proxy repository.