update docs on gateawy, session keys & testnet by zkokelj · Pull Request #101 · ten-protocol/ten-documentation

zkokelj · 2026-02-12T13:56:58Z

No description provided.

badgersrus

Looks much better, nice one @zkokelj! Couple of minor tweaks to improve readability

badgersrus · 2026-02-12T17:21:07Z

docs/4-write-ten-dapp/4-session-keys.md

+```

-## Example implementation
+The gateway validates that the session key belongs to the user identified by `encryptionToken`, signs the transaction with the session key’s private key, and propagates it to the TEN node.


This sentence made it a little difficult to read. Could be something like:

The gateway first confirms that the session key belongs to the user identified by encryptionToken. It then signs the transaction with the session key’s private key and sends it to the TEN node.

badgersrus · 2026-02-12T17:21:37Z

docs/4-write-ten-dapp/4-session-keys.md

-  // This would be a normal transaction signed by the user's wallet
-  // transferring ETH to the session key address
-}
+This path is used in integration tests and may be preferred when your client already expects standard `eth_sendTransaction` semantics. The exact UX and error handling (e.g. non‑session‑key `from`) should follow the gateway implementation.


could we add a link to the gateway implementation?

I decided that is it better to explain it more here in docs and not link to the source code as it is not that easy to read for someone who just wants to use session keys.

badgersrus · 2026-02-12T17:24:17Z

docs/4-write-ten-dapp/6-testnet.md

 # Testnet

-TEN Sepolia is our testnet that replicates the capabilities of the TEN Mainnet network. Linked to the Sepolia testnet, you can authenticate with the testnet TEN gateway, use the TEN faucet, and develop and deploy dApps for testing. 
+TEN Sepolia is our testnet that replicates the capabilities of the TEN Mainnet network. Linked to the Sepolia testnet, you can authenticate with the testnet TEN gateway, use the TEN faucet, and develop and deploy dApps for testing.


I think I wrote this paragraph originally (lol) but might be better worded:

TEN Sepolia is our testnet environment that mirrors the capabilities of the TEN Mainnet. In this environment, you can authenticate with the TEN testnet gateway, use the TEN faucet, and develop and deploy dApps for testing.

Replaced, both versions sound good, but the new one is clearer.

badgersrus · 2026-02-12T17:24:55Z

docs/4-write-ten-dapp/6-testnet.md

 Visit the TEN testnet gateway [here](https://testnet.ten.xyz/). Follow the on‑screen instructions to authenticate with the hosted gateway that allows you to interact with the testnet.

-## TEN Sepolia Faucet
+## Getting funds to the testnet


*Getting funds on the testnet?

badgersrus · 2026-02-12T17:25:17Z

docs/4-write-ten-dapp/6-testnet.md

+3. Choose how much Sepolia ETH you want to bridge from L1 to L2 (TEN).
+4. Confirm the transaction in your wallet and wait for it to finalize.

+## TEN Scan


badgersrus · 2026-02-12T17:25:58Z

docs/4-write-ten-dapp/9-programmable-gateway-access.md

+**Endpoint:** `POST /v1/join/`

-Generates and returns an EncryptionToken.
+Creates a new gateway user, generates a fresh viewing key pair, and returns the corresponding **encryption token** (also called “gateway token”) as a hex string. This token is used with both HTTP endpoints and JSON‑RPC.


*This is used with HTTP and JSON-RPC endpoints

badgersrus · 2026-02-12T17:26:44Z

docs/4-write-ten-dapp/9-programmable-gateway-access.md

+**Endpoint:** `POST /v1/getmessage/`

-Generates and returns a message (if needed 712 typed message too) for the user to sign based on the provided encryption token.
+Generates and returns an authentication message for the user to sign based on the provided encryption token. The gateway can return either an EIP‑712 typed message or a `personal_sign` message.


When does it return EIP-712 vs personal_sign? I guess from a users perspective I'd be wondering what the difference is and if its deterministic

badgersrus · 2026-02-12T17:30:00Z

docs/4-write-ten-dapp/9-programmable-gateway-access.md

+      "token": "<hex user token>"
+    }
+    ```
+  - Validates the token, checks that the user exists, and sets a long‑lived `HttpOnly`, `Secure` cookie for use by browser dApps.


Not sure if this just the PR review view of this but appears to be some weird formatting?

badgersrus

lgtm

zkokelj added 3 commits February 12, 2026 14:55

session keys

b81ccdf

programmable access

1bdd6ee

testnet

3a302aa

badgersrus reviewed Feb 12, 2026

View reviewed changes

fixes after review

611fcfa

badgersrus approved these changes Feb 13, 2026

View reviewed changes

zkokelj merged commit d9300de into main Feb 13, 2026
1 check passed

zkokelj deleted the ziga/docs_gw_sessionKeys_testnet branch February 13, 2026 12:43

Conversation

zkokelj commented Feb 12, 2026

Uh oh!

badgersrus 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!

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!

badgersrus left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants