feat: tee solver registry, vault and server by think-in-universe · Pull Request #1 · aurora-is-near/tee-solver

think-in-universe · 2025-06-02T16:02:42Z

NEAR Intents TEE Solver Registry

The NEAR Intents TEE Solver Registry is a protocol that enables secure and private execution of NEAR Intents solvers using Trusted Execution Environment (TEE) technology. This project consists of smart contracts for managing solver registration and a server for launching and managing TEE solvers.

This protocol allows liquidity pools creation for NEAR Intents. Liquidity providers can transfer funds into the pools' smart contracts. Only the solvers who're running within TEE with the approved Docker images can be registered and authorized to operate against the pools' assets.

Components

Smart Contracts

solver-registry: Support liquidity pools creation. Manage registration and verification of TEE solvers for each liquidity pool.
intents-vault: The vault contract that manage the pool's asset within NEAR Intents.

Solver Management Server

Monitoring liquidity pools and CVMs
Start TEE solvers for a newly created liquidity pool

TEE enabled AMM Solver

Intents AMM Solver within TEE (docker image)

TODOs

bowenwang1996 · 2025-06-02T22:44:55Z

contracts/solver-registry/src/events.rs

+    AddLiquidity {
+        pool_id: &'a AccountId,
+        account_id: &'a AccountId,
+        amounts: &'a Vec<U128>,
+    },
+    RemoveLiquidity {
+        pool_id: &'a AccountId,
+        account_id: &'a AccountId,
+        amounts: &'a Vec<U128>,
+    },


I don't think these two are needed. The flow is basically that once a token graduates from the launchpad, it calls create_liquidity_pool with the tokens left in the launchpad

yes. As discussed, this will be considered for next milestones. We'll skip adding/removing liquidity features in this PR.

bowenwang1996 · 2025-06-02T22:58:55Z

contracts/solver-registry/src/lib.rs

+
+        log!("verify result: {:?}", result);
+
+        // TODO: verify predecessor implicit account is derived from this public key


you also need to check that this key is generated from within the TEE. This should be part of the quote verification. The RTMR3 hash should be extended with the public key, i.e, rtmr3 = hash(rmtr3 || public_key)

This has been implemented by adding the derived public key as the raw report data when generating the quote hex.

Please remove this comment then

This TODO is to verify the predecessor account's address (implicit account) matches with the public key. This can be optional.

Let me confirm and may add this enhancement later.

think-in-universe · 2025-06-10T16:41:40Z

@bowenwang1996 Hey Bowen, this PR is not perfect and has some limitations that we need to enhance as I mentioned in the PR's description, but it's ready for review. Please invite any reviewer who needs to look into this system.

r-near · 2025-06-13T01:12:34Z

server/src/config/env.ts

+
+export const ENV = requiredEnv('ENV') as Env;
+
+export function requiredEnv(name: string): string {


You can use Zod and simplify this and index.ts by quite a bit. No need for custom env management/validation

server/src/near/solver-registry.ts

r-near · 2025-06-13T01:16:22Z

server/src/near/utils.ts

@@ -0,0 +1,60 @@
+import { getConfig } from '../config';
+import { connect, KeyPair, keyStores, Near } from 'near-api-js';


Don't use near-api-js, that's actually deprecated. Use @near-js/account, @near-js/client, or @near-js/providers. It includes all the functions you've written here.

In fact, you might not even need this utils file at all

thanks. We can refactor with either near-api-js v6.0.0+ or @near-js/* packages later in another PR.

I'll keep the utils in this PR.

near-api-js as a package is deprecated. v6 recommended moving to @near-js. It's all part of the same monorepo, which can be a bit confusing

https://github.com/near/near-api-js

r-near · 2025-06-13T01:19:22Z

server/src/phala/api/client.ts

+import axios, { AxiosInstance, AxiosRequestConfig } from 'axios';
+import { getApiKey } from '../utils/credentials';
+import { logger } from '../../utils/logger';


Why vendor this library? You can npm install it and import the APIClient instead.

It'll be a lot to manually maintain this and keep it synced with https://github.com/Phala-Network/phala-cloud-cli

Ideally yes, but I think ApiClient is not exported in the phala package.

How do you think we can import ApiClient?

They do export it here: https://github.com/Phala-Network/phala-cloud-cli/blob/main/src/api/client.ts#L18

However, I see that the package.json bundles the code, and installing from Git doesn't really help either, since it's expecting built-files only. Another option would be to fork it to support importing it as a library.

[Feature] Expose src/api as an importable library module Phala-Network/phala-cloud-cli#33

feat: Expose src/api as an importable library module Phala-Network/phala-cloud-cli#34

Just opened an issue in the repo and a corresponding PR to fix that. If/once they merge, then we no longer need to vendor this library 😄

r-near · 2025-06-13T01:21:44Z

server/src/near/solver-registry.ts

+  }
+
+  public async getWorkerLen(): Promise<number> {
+    await this.init();


No need for multiple inits - you can move this to a constructor, or if you'd prefer, just make everything static methods and keep the inits.

That was supposed to use constructor in the initial implementation, but constructor function cannot be async. We can refactor this later.

So it looks like:
init() calls getConfig() which is async
getConfig() dynamically imports either mainnet.ts or testnet.ts based on the ENV variable
But ENV is determined at module load time from process.env.ENV

constructor() { // This could be done synchronously since ENV is available immediately const config = ENV === 'mainnet' ? mainnetConfig : testnetConfig; this.solverRegistryContract = config.near.contract.solverRegistry; }

Also dynamically importing modules is not really ideal.

I agree. make sense. will update this later.

r-near · 2025-06-13T01:24:17Z

server/tsconfig.json

+{
+  "compilerOptions": {
+    "target": "ES2020",
+    "module": "commonjs",


No need for commonjs support, that's a legacy setting

r-near · 2025-06-13T01:24:59Z

server/package.json

+    "start": "node -r dotenv/config dist/index.js",
+    "dev": "ts-node -r dotenv/config src/index.ts",
+    "test": "jest",
+    "lint": "eslint . --ext .ts"


Check out biome for linting/formatting instead of eslint

thanks. we may migrate to biome later.

server/package.json

bowenwang1996 · 2025-06-13T01:31:53Z

contracts/intents-vault/src/lib.rs

+#[near(contract_state)]
+pub struct Contract {}
+
+/// TODO: the contract can be deployed as a global contract


Let's create an issue for this one

The issue has been created: #3

bowenwang1996 · 2025-06-13T01:32:40Z

contracts/solver-registry/src/lib.rs

+
+        log!("verify result: {:?}", result);
+
+        // TODO: verify predecessor implicit account is derived from this public key


Please remove this comment then

bowenwang1996 · 2025-06-13T01:33:06Z

contracts/solver-registry/src/lib.rs

+    // fn require_approved_codehash(&self) {
+    //     let worker = self.get_worker(env::predecessor_account_id());
+    //     self.assert_approved_codehash(&worker.codehash);
+    // }


why is this commented out?

This assertion function is used when the worker invokes some functions via the registry contract (e.g. get Chain Signatures of some intents via a sign_intents function), but in practice we didn't use this function yet. I prefer keep the commented code for now, and we can remove it later if there's no such use case.

bowenwang1996 · 2025-06-13T01:33:37Z

contracts/solver-registry/src/pool.rs

+    // `add_liquidity` and `remove_liquidity` are not needed for now
+    // #[payable]
+    // pub fn add_liquidity(
+    //     &mut self,
+    //     pool_id: u32,
+    //     token_ids: Vec<AccountId>,
+    //     amounts: Vec<Balance>,
+    // ) {
+    //     require!(token_ids.len() == 2, "Must have exactly 2 tokens");
+    //     require!(amounts.len() == 2, "Must have exactly 2 amounts");
+    //     require!(amounts[0] > 0, "Amount must be greater than 0");
+    //     require!(amounts[1] > 0, "Amount must be greater than 0");
+
+    //     let pool = self.pools.get(pool_id).expect("Pool not found");
+    //     let shares_total_supply = pool.shares_total_supply;
+    // }
+
+    // #[payable]
+    // pub fn remove_liquidity(&mut self, pool_id: u32, shares: U128) {
+    //     let shares = shares.0;
+    //     require!(shares > 0, "Shares must be greater than 0");
+
+    //     let pool = self.pools.get(pool_id).expect("Pool not found");
+    //     // pool.shares_total_supply -= shares;
+    // }
+}


Let's create an issue for allowing users to add liquidity

Yes. I have created an issue: #2

r-near · 2025-06-15T17:06:50Z

server/package.json

+  "devDependencies": {
+    "@types/jest": "^29.5.0",
+    "@types/node": "^18.15.11",
+    "@typescript-eslint/eslint-plugin": "^5.57.1",


This is several major versions behind. The latest is 8.34.0

r-near · 2025-06-15T17:07:06Z

server/package.json

+    "@types/node": "^18.15.11",
+    "@typescript-eslint/eslint-plugin": "^5.57.1",
+    "@typescript-eslint/parser": "^5.57.1",
+    "eslint": "^8.37.0",


This is a major version behind, the latest is 9.29.0

r-near · 2025-06-15T17:07:36Z

server/package.json

+  },
+  "devDependencies": {
+    "@types/jest": "^29.5.0",
+    "@types/node": "^18.15.11",


Node 18 is being deprecated in 1 month

r-near · 2025-06-15T17:08:42Z

server/package.json

+    "jest": "^29.5.0",
+    "ts-jest": "^29.1.0",
+    "tsx": "^4.20.3",
+    "typescript": "^5.0.3"


This version of typescript is over a year old

Thanks! I'll update the dependencies this week.

think-in-universe added 5 commits June 2, 2025 22:03

feat: solver registry and intents vault contracts

8b3af87

fix: build error

6cf9c24

feat: fix build error

467e6ab

ci: build and test

db0b4c8

style: code format

0044769

think-in-universe changed the title ~~feat: solver registry and intents vault~~ [WIP] feat: solver registry and intents vault Jun 2, 2025

think-in-universe added 2 commits June 3, 2025 00:21

feat: tee solver server

48e7a9a

fix: assert owner

2c8ffda

think-in-universe changed the title ~~[WIP] feat: solver registry and intents vault~~ [WIP] feat: tee solver registry, vault and server Jun 2, 2025

bowenwang1996 reviewed Jun 2, 2025

View reviewed changes

think-in-universe added 20 commits June 4, 2025 02:22

test: mock intents contract for testing

8cfe098

fix: integration test failures

813d9e0

style: code format

d59c4c6

ci: fix test failure

fa659e8

refactor: disbale add/remove liquidity

c870217

feat: view functions

6d44827

style: code format

dc2a3e4

feat: deposit into pool

07b4a06

style: comment

2173e0b

fix: deposit into pool incorrect refund

38a4d13

fix: two tokens cannot be identical

923a8c3

style: code format

1c36e07

feat(server): deploy solvers

aa6147f

feat(server): fund solvers with initial balances

b82d73f

chore: update solver codehash

1876518

chore: update solver codehash

f7dbb35

chore: contract wasm files

ab489f5

chore: mainnet deployment

34932d0

chore: update tee solver code hash

cbef73d

chore: update scripts

f712103

think-in-universe changed the title ~~[WIP] feat: tee solver registry, vault and server~~ feat: tee solver registry, vault and server Jun 9, 2025

think-in-universe added 11 commits June 10, 2025 18:26

feat: verify public key with remote attestation report data

ac71c67

chore: deploy solver registry in testnet

4937c30

fix: parse public key

dfab19a

chore: update solver registry wasm file

e1a628f

fix: pad the public key hex with 0 to 128 bytes

499c8e0

chore: update solver registry wasm file

8af3725

refactor: contract

fe53bfc

chore: update solver registry wasm file

7472c8d

test: ignore integration test which won't succeed

5241482

feat: update readme and env vars

0a76baa

docs: update readme

c4a8d70

think-in-universe added 3 commits June 11, 2025 00:46

docs: update the readme

aefc173

docs: update readme

9f2acad

style: fix comment

2214455

r-near reviewed Jun 13, 2025

View reviewed changes

bowenwang1996 approved these changes Jun 13, 2025

View reviewed changes

chore: replace ts-node with tsx

dc79a28

think-in-universe merged commit 4543305 into main Jun 15, 2025
5 checks passed

think-in-universe deleted the feat/tee-solver branch June 15, 2025 17:02

r-near reviewed Jun 15, 2025

View reviewed changes


		log!("verify result: {:?}", result);

		// TODO: verify predecessor implicit account is derived from this public key


		export const ENV = requiredEnv('ENV') as Env;

		export function requiredEnv(name: string): string {

		@@ -0,0 +1,60 @@
		import { getConfig } from '../config';
		import { connect, KeyPair, keyStores, Near } from 'near-api-js';

Conversation

think-in-universe commented Jun 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

NEAR Intents TEE Solver Registry

Components

Smart Contracts

Solver Management Server

TEE enabled AMM Solver

TODOs

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

think-in-universe commented Jun 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

think-in-universe commented Jun 2, 2025 •

edited

Loading

think-in-universe commented Jun 10, 2025 •

edited

Loading