docs: testnet with tee support guide #1604

barakeinav1 · 2025-12-03T12:25:16Z

fixes #1660
related https://github.com/near/mpc-private/issues/86 and https://github.com/near/mpc-private/pull/88

netrome · 2025-12-11T10:22:59Z

fixes https://github.com/near/mpc-private/issues/86

Fixing a private issue in a public PR feels a bit odd. It would be nice to have a dedicated public issue in this repo explaining that we have set up a cluster (we can still link to the private one about the setup), and that we should have a guide that helps anyone set up their own TEE testnet clusters.

Not a hard blocker though.

netrome

Some questions and comments, but nothing blocking.

docs/localnet/TEE_localnet.md

netrome · 2025-12-11T10:28:37Z

docs/testnet/args/init_testnet_tee.json

Instead of creating a new file, we could reuse the existing docs/localnet/args/init.json template and just add an env var for the port.

There are several differences between init.json and the nit_testnet_tee.json (different port ranges, IPs, and configurable account names).
I'm not saying it doesn't make sense to merge them together, but the overhead now (updating all localnet+localnet_TEE docs), is a but too much.

We can do this in a follow-up PR if really needed.

docs/testnet/setup_guide_for_testnet_with_tee_support.md

netrome · 2025-12-11T10:30:23Z

docs/testnet/setup_guide_for_testnet_with_tee_support.md

+
+## Step 1: Create MPC Account
+
+Since the faucet gives only **10 NEAR per account** (and the MPC contract storage costs **15 NEAR**),  


Can't you run the faucet multiple times for the same account?

Are we sure there is no way to do this instead of the indirection? I'd advise to send a message to the SDK guys on telegram to ask for this. They are very responsive and helpful.

CC: @r-near

If you're using near-cli this is probably the simplest way to do it

@r-near I didn't understand your answer. is there a way to create an account with more than 10 near using faucet account? or fund it multiple time to achieve the same thing? if yes, can you provide the command (or link) ? I didn't find anything about this in documentation.

Are we sure there is no way to do this instead of the indirection? I'd advise to send a message to the SDK guys on telegram to ask for this. They are very responsive and helpful.

do you mean this https://t.me/neardev ?

DSharifi

Looks good.

2 changes that are blocking:

I think you updated libs/nearcore by mistake

Don't hardcode barak_tee_test1_ as a prefix to the account names in your tests. I think we can reuse the approach for the current devnet README, where there are placeholders for the account name to use:

mpc/crates/devnet/README.md

Lines 92 to 94 in a7c1489

    
           First, create an MPC network. Pick a name; here I'll use 
        
           "MPC_NETWORK_NAME=yourusername-test", but **ensure that your name is globally unique 
        
           within the team**, so include your username in there.

DSharifi · 2025-12-11T12:36:11Z

deployment/testnet/sam.conf

+MPC_ACCOUNT_ID=barak_tee_test1_sam.testnet
+MPC_LOCAL_ADDRESS=127.0.0.1
+MPC_SECRET_STORE_KEY=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
+MPC_CONTRACT_ID=barak_tee_test1_mpc.testnet


I don't think the guide should have a hard coded testnet name with your firstname in it. Can we make the name more generic like we have in the other guides?

DSharifi · 2025-12-11T12:43:00Z

docs/testnet/setup_guide_for_testnet_with_tee_support.md

+
+## Step 1: Create MPC Account
+
+Since the faucet gives only **10 NEAR per account** (and the MPC contract storage costs **15 NEAR**),  


Are we sure there is no way to do this instead of the indirection? I'd advise to send a message to the SDK guys on telegram to ask for this. They are very responsive and helpful.

barakeinav1 · 2025-12-14T08:51:27Z

Fixing a private issue in a public PR feels a bit odd. It would be nice to have a dedicated public issue in this repo explaining that we have set up a cluster (we can still link to the private one about the setup), and that we should have a guide that helps anyone set up their own TEE testnet clusters.

sure:
I create an public task: #1660 and link to it.
and private task https://github.com/near/mpc-private/issues/86 is close by private PR https://github.com/near/mpc-private/pull/88

Co-authored-by: Daniel Sharifi <[email protected]>

barakeinav1 · 2025-12-14T11:54:50Z

I think you updated libs/nearcore by mistake

fixed

barakeinav1 · 2025-12-14T12:05:54Z

2. Don't hardcode barak_tee_test1_ as a prefix to the account names in your tests. I think we can reuse the approach for the current devnet README, where there are placeholders for the account name to use:

good idea

barakeinav1 changed the title ~~Barak/doc/testnet tee~~ feat: testnet with tee support guide Dec 4, 2025

netrome changed the base branch from main to barak/doc/update_localnet_guide December 4, 2025 20:41

Base automatically changed from barak/doc/update_localnet_guide to main December 5, 2025 10:15

barakeinav1 force-pushed the barak/doc/testnet_tee branch 2 times, most recently from 3391ad2 to d772ef2 Compare December 10, 2025 06:44

netrome previously approved these changes Dec 11, 2025

View reviewed changes

DSharifi changed the title ~~feat: testnet with tee support guide~~ docs: testnet with tee support guide Dec 11, 2025

DSharifi requested changes Dec 11, 2025

View reviewed changes

barakeinav1 and others added 20 commits December 14, 2025 09:14

WIP before rebase

d520399

ip fix

79ca9a9

hash update

19d1271

some updates

36083e0

dashboard

73b3d87

adding scripts

e6aaa5b

update vote commands

9aee5b9

update get allow hashes command

4e92669

use latest image tag

3cf8003

comment out EXTERNAL_MPC_DECENTRALIZED_STATE_SYNC port

a9ca58f

typo in frodo

6c32390

Update docs/localnet/TEE_localnet.md

8c2229b

Co-authored-by: Daniel Sharifi <[email protected]>

Update docs/localnet/TEE_localnet.md

a41c6bc

Co-authored-by: Daniel Sharifi <[email protected]>

review fixes

1ad01aa

review fixes

02db180

tag fix

3684872

mroe fixes

55681c7

update after reproducation of the setup

0273e03

doc updates

e928aab

small fixes

ed04b86

barakeinav1 added 9 commits December 14, 2025 09:14

fix IP

86327e3

adjust ports and paths

449ec37

doc update

7b36b23

testnet with tee testing

99da713

add files

067ac8f

Reset frodo.env and sam.env to main version

253bb36

small udpates

89ea59a

Proofreading fixes

c56bad7

launcher_docker_compose.yaml

77693ad

barakeinav1 dismissed netrome’s stale review via 77693ad December 14, 2025 09:16

barakeinav1 force-pushed the barak/doc/testnet_tee branch from d772ef2 to 77693ad Compare December 14, 2025 09:16

barakeinav1 added 3 commits December 14, 2025 09:23

Sync localnet docs and env files from main

8afce16

Remove one-server testnet files (moved to separate branch)

f718117

cleaup temp files

a14821f

barakeinav1 added 2 commits December 14, 2025 12:25

make account names generic

245a4c6

make account names configurable

a5e52c5

barakeinav1 mentioned this pull request Dec 14, 2025

feat(doc): Support running two MPC CVMs (Frodo + Sam) on the same physical machine #1661

Draft

barakeinav1 requested review from DSharifi and netrome December 15, 2025 09:46


		## Step 1: Create MPC Account

		Since the faucet gives only 10 NEAR per account (and the MPC contract storage costs 15 NEAR),

	First, create an MPC network. Pick a name; here I'll use
	"MPC_NETWORK_NAME=yourusername-test", but **ensure that your name is globally unique
	within the team**, so include your username in there.

docs: testnet with tee support guide #1604

Are you sure you want to change the base?

docs: testnet with tee support guide #1604

Conversation

barakeinav1 commented Dec 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

netrome commented Dec 11, 2025

Uh oh!

netrome left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

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!

DSharifi left a comment

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!

barakeinav1 commented Dec 14, 2025

Uh oh!

barakeinav1 commented Dec 14, 2025

Uh oh!

barakeinav1 commented Dec 14, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

barakeinav1 commented Dec 3, 2025 •

edited

Loading