git.iko.soy/urbit.org
on master help sign in
Merge pull request #513 from urbit/escape-sponsor
d945d13poprox
content/using/operations/using-bridge.md+38
compare with master
unifiedsplit
@@ -73,3 +73,41 @@ From the detail page associated with your point, click the `Generate Arvo Keyfil
73Click `Generate ->`, which will download a keyfile onto your machine.
73Click `Generate ->`, which will download a keyfile onto your machine.
74
74
75With that keyfile in hand, you can now exit Bridge and continue to the guide to [install the Urbit binary](@/using/install.md).
75With that keyfile in hand, you can now exit Bridge and continue to the guide to [install the Urbit binary](@/using/install.md).
76+
77+### Escaping your sponsor
78+
79+As a planet or star, it behooves you to be sponsored by an active star or galaxy,
80+respectively. If your sponsor isn't suiting your needs, you can escape to a
81+different one.
82+
83+#### Prerequisites
84+
85+- A little bit of ETH in your management proxy address to pay for the
86+ transaction.
87+- The `@p` of the sponsor you want to escape to. You should negotiate the
88+ transfer with the sponsor ahead of time, as they will need to accept it on
89+ their end. If you cannot find one, contact Tlon at support@urbit.org and we
90+ will assist you in escaping to one of our stars/galaxies.
91+
92+#### Instructions
93+
94+1. Login to [Bridge](https://bridge.urbit.org) with the management proxy address
95+ for the ship that will be escaping their sponsor. The ownership address will
96+ also do, as will the master ticket if you have that.
97+2. Click on the "OS" button at the bottom of the screen.
98+3. Below Network, you will find the `@p` of your current sponsor. Click "Change"
99+ to the right of that.
100+4. Enter the `@p` of your new sponsor.
101+5. Click the "Request" button and then complete the transaction.
102+
103+This action will consume a small amount of ETH. Your sponsor will then need to
104+accept you via a similar process in Bridge, which will require ETH on their end.
105+After the transaction is completed on Ethereum, it will still take some time for
106+the information to propagate to the Urbit network. After 30 minutes or so, you
107+may check that your sponsor has successfully been altered by running
108+`(sein:title our now our)` in dojo and confirming that the `@p` matches that of
109+your new sponsor.
110+
111+Once you change your sponsor, you will likely want to change your source of
112+[OTAs](@/docs/glossary/ota-updates.md) to them as well. To accomplish this, enter `|ota
113+~sponsor %kids` in dojo, where `~sponsor` is the `@p` of your new sponsor.
content/using/operations/using-your-ship.md+5−22
@@ -185,28 +185,11 @@ To cycle the keys of a moon without breaching, run:
185
185
186### Escaping A Sponsor {#escape}
186### Escaping A Sponsor {#escape}
187
187
188−To use the network as a planet or star, you must be sponsored by an active star or galaxy, respectively. If your sponsor isn't suiting your needs, you can escape to a different one. The [Bridge](https://bridge.urbit.org/) software doesn't yet support escaping. For the time being, however, you can follow this guide.
188+To use the network as a planet or star, you must be sponsored by an active star
189−
189+or galaxy, respectively. If your sponsor isn't suiting your needs, you can
190−#### Prerequisites
190+escape to a different one. This can be done with
191−
191+[Bridge](https://bridge.urbit.org/) following the instructions
192−- A little bit of ETH in your management proxy address to pay for the transaction.
192+[here](@/using/operations/using-bridge.md#escaping-your-sponsor).
193−- The identity number of the sponsor you want to escape from.
194−- The identity number of the sponsor you want to escape to.
195−
196−You can find an identity's number by running ``` `@`~marzod ``` in any Dojo, where `~marzod` is the name of the relevant identity.
197−
198−#### Instructions
199−
200−0. If you have your management proxy in Metamask, you can use Etherscan [here](https://etherscan.io/address/ecliptic.eth#writeContract). Skip steps 1-4.
201−1. Go to either myetherwallet.com or mycrypto.com. Since this is a low-risk operation, and you're signing with a low-value key, it's fine to use their online versions. Sign in with your management mnemonic. (They may still force you to download their tool to log in like this.)
202−2. Navigate to the "interact with contract" page of the tool you're using.
203−3. Specify a contract address of `0x6ac07B7C4601B5CE11de8Dfe6335B871C7C4dd4d`.
204−4. Copy the "contract ABI" from [here](https://etherscan.io/address/ecliptic.eth#code) and paste it into the "ABI/JSON interface" field.
205−5. Select the `escape()` function, passing in two arguments: your identity number, and the number of your desired sponsor.
206−6. Sign and submit the transaction.
207−7. Get in touch with your prospective sponsor, since they won't be notified otherwise. You can do this by contacting them on the network via chat, or joining `~bitbet-bolbel/urbit-community` and asking around.
208−8. Wait for your request to be accepted by the prospective sponsor.
209−9. If your request is not accepted by your prospective sponsor, a last resort, you can make a request to escape to `~marzod`, which is operated by Tlon, the company leading the development of Urbit.
210
193
211### Continuity breaches
194### Continuity breaches
212
195