Skip to content

docs: create a guide for localnet + MPC node running in TEE setup#1456

Merged
barakeinav1 merged 32 commits intomainfrom
barak/doc/update_localnet_guide
Dec 5, 2025
Merged

docs: create a guide for localnet + MPC node running in TEE setup#1456
barakeinav1 merged 32 commits intomainfrom
barak/doc/update_localnet_guide

Conversation

@barakeinav1
Copy link
Contributor

Create a guide for localnet + MPC note running in TEE setup
fixes #1417

@barakeinav1 barakeinav1 force-pushed the barak/doc/update_localnet_guide branch 2 times, most recently from 005f7c8 to 36b4a31 Compare November 16, 2025 10:11
@DSharifi DSharifi self-requested a review November 16, 2025 18:57
@DSharifi DSharifi changed the title Create a guide for localnet + MPC note running in TEE setup docs: create a guide for localnet + MPC node running in TEE setup Nov 16, 2025
Copy link
Contributor

@DSharifi DSharifi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Posting my findings so far. The Review is incomplete as I am not able to reproduce.

Overall it's a very nice written guide.

The helper scripts need some more work. I've tried debugging them for a while, but haven't gotten much progress, so let's try going over this tomorrow together @barakeinav1

The scripts are quite fragile, and it requires a lot of manual setting of ports, because the default ports are hard coded on a TDX machine that is shared. Ideally the scripts should try to bind to an available port and expose this instead.

@barakeinav1 barakeinav1 force-pushed the barak/doc/update_localnet_guide branch 3 times, most recently from 45218cc to c7b0aad Compare November 19, 2025 15:30
@DSharifi DSharifi self-requested a review November 27, 2025 10:31
Copy link
Contributor

@DSharifi DSharifi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just

Copy link
Contributor

@DSharifi DSharifi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These ports need to be updated to correspond with the localnet ports we initialize the contract with

@DSharifi
Copy link
Contributor

DSharifi commented Dec 2, 2025

Stacked a PR on top with fixes to the Ports and /tmp/ file issue.

#1597

@barakeinav1 barakeinav1 force-pushed the barak/doc/update_localnet_guide branch from 4c9102d to 2edd694 Compare December 2, 2025 14:11
netrome
netrome previously approved these changes Dec 4, 2025
Copy link
Collaborator

@netrome netrome left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't done a deep review, but from what I can see this looks pretty good. I have some suggestions and thoughts but overall looks good.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Naturally the same changes as I suggested in frodo.env should be changed here as well.


#### 4. Replace ${MACHINE_IP} inside the config files
```bash
sed -i "s|\${MACHINE_IP}|$MACHINE_IP|g" ../deployment/localnet/tee/frodo.conf
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Recommendation: I used envsubst for these kinds of substitutions already in the localnet guide. I think we could use it instead of sed here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

envsubst can't do inline editing, so it complicates things a bit.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer generating a new file (e.g. /tmp/localnet/frodo.conf) over inline editing since these files are version controlled and should not be modified in the repo. But sure, not a hard blocker.

Copy link
Contributor

@gilcu3 gilcu3 Dec 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this mean that if I follow the guide, a file that is tracked in git is modified, and will need to be reverted back afterwards to avoid committing it by mistake? If yes, then I second the /tmp/... file copy preference, the other way seems a bit annoying for devs.


---

## Add a Domain
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This part is the same as in the localnet guide already? Perhaps we could just reference it there? Although I don't mind a little duplication of these commands since they should be very stable and not subject to change.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, it is a duplication, but since this is a small step at the end I think it is ok to leave it there.

@barakeinav1 barakeinav1 added this pull request to the merge queue Dec 5, 2025
Merged via the queue into main with commit fe81577 Dec 5, 2025
13 checks passed
@barakeinav1 barakeinav1 deleted the barak/doc/update_localnet_guide branch December 5, 2025 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Create a guide for localnet + MPC note running in TEE setup

4 participants