Skip to content

Commit a2e2349

Browse files
Document current problem waiting for the 'init' event
1 parent 6a7f6f2 commit a2e2349

File tree

1 file changed

+15
-8
lines changed

1 file changed

+15
-8
lines changed

README.md

Lines changed: 15 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,25 +4,32 @@ WORK IN PROGRESS
44

55
The idea is to run ledgerloops over peer-to-peer messaging links powered by [Cabal](https://cabal.chat).
66

7+
FIXME: The `init` event is not arriving.
8+
When messages do arrive, it's very slow (20 seconds or so).
9+
I'll ask around at [P4P unconference](https://offline.place/events/2024/05/24/p4p-unconference/) to find out what I'm doing wrong here.
10+
711
Usage:
812
```
913
git clone https://github.com/ledgerloops/ledgerloops-cabal
1014
cd ledgerloops-cabal
1115
npm install
1216
npm run build
13-
npm start
17+
npm start alice bob
1418
```
1519

1620
In a separate window:
1721
```
18-
npx cabal --temp 411dbe21d6f8e222733ac88d2da3cf953aa9f5466db94fa9fa967a765be3875e
22+
npm start bob alice
23+
```
24+
Alice and Bob will try to connect to a Cabal between them, namely
25+
`14011c8dc710dc387a64d44e942bd0d60f35e5f4975917d6a3a014ee16222b91`
26+
which happens to be `sha256('alice-bob')`.
27+
28+
So in yet another window you can do this to listen in:
29+
```
30+
npx cabal --temp 14011c8dc710dc387a64d44e942bd0d60f35e5f4975917d6a3a014ee16222b91
1931
> /join default
32+
> /nick yourmaker
2033
> hello there
2134
```
2235

23-
You will see the messaging working.
24-
25-
Next step: set up a number of nodes, with links between them, for instance in an hourglass topology like [the one from Strategy Pit](https://github.com/ledgerloops/strategy-pit?tab=readme-ov-file#hour-glass), and then run [Saiga nodes](https://github.com/ledgerloops/strategy-pit?tab=readme-ov-file#-saiga)
26-
and see if they find loops and resolve them.
27-
28-
For this, I'll need one proces per node.

0 commit comments

Comments
 (0)