π
TRUSTLESS VAULT
TEE-SECURED FUND MANAGEMENT β VERIFIED BY ATTESTATION
connecting...
scan #
-
Β·
-
Vault
address
-
status
-
total deposited
-
P&L
-
Market
BTC
...
ETH
...
SOL
...
Active Signals
waiting for data...
Rules Β· Hardcoded Β· Immutable Β· Attestable
π‘οΈ
Max loss per trade
-
π
Max single position
-
π«
Stop loss
-
π
Funding threshold
-
βΈοΈ
Cooldown after loss
-
π―
Allowed assets
-
Why This Needs TEE
question
without TEE β with TEE
Who holds the key?
a person
β
hardware (nobody)
Can rules change secretly?
yes
β
no β attestation breaks
Can someone steal funds?
yes, with the key
β
no β key in silicon
How to verify strategy?
read whitepaper, hope
β
read code, check hash
Verify This Vault
Run
phala cvms attestation trustless-vault
Note the
compose_hash
from the event log
Hash the
docker-compose.yaml
yourself β must match
Read
vault.py
β the rules are right there, hardcoded
Any change to code = different hash = attestation breaks