# \[Rust\] Interledger-rs accounts architecture

**URL:** https://forum.interledger.org/t/rust-interledger-rs-accounts-architecture/645
**Category:** Implementations and SDKs
**Created:** [June 19, 2019, 11:14pm UTC](https://forum.interledger.org/t/rust-interledger-rs-accounts-architecture/645 "2019-06-19T23:14:54Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Ayush](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.interledger.org/ayush/32/332_2.png) [@Ayush](https://forum.interledger.org/u/Ayush)
#### Post date: [June 19, 2019, 11:14pm UTC](https://forum.interledger.org/t/rust-interledger-rs-accounts-architecture/645/1 "2019-06-19T23:14:55Z")

</div>

I’ve been exploring the Rust implementation of ILP.

> **[interledger-rs/interledger-rs](https://github.com/interledger-rs/interledger-rs)**
>
> An easy-to-use, high-performance Interledger implementation written in Rust - interledger-rs/interledger-rs

The Accounts abstraction seems to handle a lot of functionality. Accounts can track the owner of a node, other connectors that are peers of node, or users (customers) connected to the node. This brings me to a couple questions:

Who writes the users account to the node? If it’s some sort of wallet, will that wallet need to run an ILP node?

---

<div class="post-metadata">

### Author: ![emschwartz](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.interledger.org/emschwartz/32/12_2.png) [@emschwartz](https://forum.interledger.org/u/emschwartz)
#### Post date: [June 19, 2019, 11:32pm UTC](https://forum.interledger.org/t/rust-interledger-rs-accounts-architecture/645/2 "2019-06-19T23:32:20Z")

</div>

Hi Ayush,

Good question. You’re right that a lot in interledger.rs is based around the Account model.

Right now, the node admin needs to add users’ Accounts with a POST to the `/accounts` HTTP API endpoint. While that is fine for two nodes who are explicitly peering with one another, it’s a bit of a laborious process.

In the future, we may add functionality for “auto-peering” or “easy peering”, which would make the Account creation process more automatic. For the status of that feature set, see [Auto-Peering, Easy Peering, and Open Signup](https://forum.interledger.org/t/auto-peering-easy-peering-and-open-signup/556).

---

<div class="post-metadata">

### Author: ![Ayush](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.interledger.org/ayush/32/332_2.png) [@Ayush](https://forum.interledger.org/u/Ayush)
#### Post date: [June 20, 2019, 6:26pm UTC](https://forum.interledger.org/t/rust-interledger-rs-accounts-architecture/645/3 "2019-06-20T18:26:01Z")

</div>

So the node admin writes users’ Accounts using a POST request. Then should there be some sort of authorization added to the request body? Or are connectors allowed to write Accounts on other peers.

Considering this, it’s probably useful for some user facing service on ILP to run nodes and peer with a good variety of connectors.
