# Auto-Peering, Easy Peering, and Open Signup

**URL:** <https://forum.interledger.org/t/auto-peering-easy-peering-and-open-signup/556>\
**Category:** Protocol Design\
**Tags:** peering\
**Created:** [April 30, 2019, 4:12pm UTC](https://forum.interledger.org/t/auto-peering-easy-peering-and-open-signup/556 "2019-04-30T16:12:32Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:** [April 30, 2019, 10:14pm UTC](https://forum.interledger.org/t/auto-peering-easy-peering-and-open-signup/556/5 "2019-04-30T22:14:23Z")

</div>

Excellent points! Based on this thread, I’m leaning towards:

- Auto-Peering -\> non-goal, based on the reasoning @ekrenzke outlined
- Easy-Peering -\> nice to have, but maybe not super high priority until we have a manual flow we’ve tried out and are trying to automate
- Open Signup -\> keep using BTP for this, in order to support non-server clients as @kincaid mentioned

Unless others vehemently disagree with these conclusions, this suggests that we don’t have any more to do on this right now and should instead focus on finalizing [settlement](https://forum.interledger.org/t/settlement-architecture/545) and the [ledger / settlement system abstraction](https://forum.interledger.org/t/ledger-adapter-api/553).

---

_[View the full topic](https://forum.interledger.org/t/auto-peering-easy-peering-and-open-signup/556)._