1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
Networking
----------
Part 0: Introduction
--------------------
There are various ways of achieving a network in arching-kaos and some of them
are documented here. The ones that are missing, either their are under testing,
considered to be covered or not yet grasped.
Part 1: Preassumptions
----------------------
This document assumes you somehow familiarized yourself with the scripts and
their usage.
Part 2: Networking via IPFS
---------------------------
We need to mention here that when you install arching-kaos-tools, IPFS is also
installed. Furthermore, a swarm key is downloaded and installed as well. This
is used to connect to aknet swarm in IPFS. Hence, you 'll need some peers to
connect to via IPFS. Ask for that in #arching-kaos over at IRC. See `SUPPORT`
file as well.
Other than that, you can make up yourself a swarm and express your creativity
there.
Part 3: Networking via Stellar Network
--------------------------------------
Stellar Network is used as a peering system. If you own an address in XLM, you
can store a named variable in your address. You 'll be required to "lock" 0.5XLM
to persist the value you want. You'll be also required to trust ARCHINGKAOS
asset if you want your content to be retrievable via https://arching-kaos.net
and contribute with your creativity there.
3.1 Assumption
--------------
We assume you already have a Stellar wallet and you also have direct access to
your private key. This will be needed in case you don't use some wallet,
compatible with https://laboratory.stellar.org/ which we will be using for
connecting our arching-kaos configuration link (aka AKID) with our Stellar
address.
3.2 Preparation
---------------
Before we publish anything, we need to know what we need to publish and where.
Issuing the command
```
ak config --get-ipns-key
```
will return to us the IPNS key that points to our current AKID.
We will need this value for the next step
3.3 Publishing IPNS key to Stellar network
------------------------------------------
1. Visit https://laboratory.stellar.org/#?network=public and go to the "Build
transaction" option,
2. Enter your Stellar address in the Source Address field,
3. Click the "Fetch next sequence number for account starting with ..." button,
4. Scroll down to find the "Operation Type" and select from the dropdown menu
the "Manage data" option,
5. Use as "Entry name": "config" (without the double quotes),
6. Paste the IPNS link we got from the previous section, in the "Entry value"
field,
7. Scroll further down and click the "Sign in Transaction Signer" button,
8. Sign the transaction with your wallet or your private key,
9. Submit the transaction to the Stellar Network!
Congratulations! You successfully published your IPNS reference to your AKID in
the Stellar Network.
3.4 Open a trustline to ARCHINGKAOS
-----------------------------------
To be able to post content on arching-kaos.net you will need to trust the asset
ARCHINGKAOS issued by GB4QVKD6NW3CSNO5TNPARAWNPPXOPSSTKB35XCWB7PUNBIQTK3DVELB2.
Build a transaction as described above, but instead of "Manage data" select
"ChangeTrust" option. Set the information above in the appropriate fields,
sign the transaction and submit it.
Now, your contributions will appear at https://arching-kaos.net
Part 4: Networking with CJDNS
-----------------------------
CJDNS is a decentralized mesh networking alternative to the internet. It uses
the fc00::/8 private space of IPv6 protocol. Your IPv6 derives from your public
key where its private part is used to decrypt your incoming packets.
Using CJDNS and arching-kaos-tools to netwok around is pretty easy but there are
steps to make it work as well. Of course, you will need CJDNS to be running in
the machine you want to network with/from. Furthermore, you will also need the
cjdns-tools, laying under the tools folder in the cjdns repository to be in your
PATH.
You then can use the `ak-cjdns-scanner` to find other akdaemon(s) running around
your relative neighbourhood. `dumpLinks` is used to retrieve the nodes in this
area. You can find more intense scanning scripts around like `walk.sh` by ircerr
which is able to reach the whole public network of cjdns.
- http://hia.cjdns.ca/watchlist/c/walk.sh (seq)
- http://hia.cjdns.ca/watchlist/c/walk2.sh (threaded)
TODO: We should be storing the output on a relevant file so it can be reached by
the API as well or ask for current known nodes without rescanning the network.
|
