Bitcoin Forum

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512


As a new moon rises over the ruins of Alexandria's Library a new technology comes into the world:

Eudaemon: A peer-to-peer electronic identity system

Release notes v1
Installer hash: 3489c9680dbaa0a84d04fbe0b84ed61bf87343a45b04a39b5ec33beb306683bd

Agathos
D3B12E8EBE4A212955B1BF13F49BD18BE5409784
With help from: Atlas, Monad, Pan, Toto and Bald Eagle

**Abstract**

By combining a small-world trust network, a peer-to-peer storage system, a fungible reputation, and personal blockchains, we create a peer-to-peer electronic identity system for individuals to secure and assert their identities and histories without requiring a central institution. At the core of this system is proof of human (PoH), a peer consensus mechanism based on asymmetric key signing and threshold signatures^{[1](#1shamir1979)}, which prevents any M-of-N peers from claiming authority over an individual's identity. Trusted peers act as relays to the greater network and provide storage and propagation of messages allowing for persistent serverless digital identity and digital interactions.

We anchor identity and associated data to our social peers using the robust and easy to recover data structure that is a personal blockchain to solve identity sovereignty and data loss problems simultaneously. This solves the general key management problem by providing secure backup and recovery of seed phrases and private keys from trusted peer groups without the need for a central authority. Personal blockchains are used instead of a classic central blockchain so no initial tokens need to be mined or purchased before being able to participate. The system enables creation of identity at birth, the restoration of identity and personal blockchain in the event of identity/device loss and the autonomous execution of digital legacy/will at death. We propose that this, when used in conjunction with traditional blockchain networks, will allow for widespread adoption of blockchain technology.

Website: eud.ninja
Git repo: git@codeberg.org:agathos/Eudaemon.git

Check and bookmark BTC transaction 9691b18bc20ad2cc37ac40464d054ef175c5f8d3430cd0f81f8f48066df412a1
The Agathian fingerprint is embedded in those transactions.
Subsequent transactions should contain the hashes of each release.

BSV transaction 0143efb868a6342b0dbf4b1e33c61058a8cf83cb042fce15b5ef9552a6cebd4e
contains the full Agathian public key.
Subsequent transactions should contain the full code and release notes of each release.

Instructions:
To install run bash Eudaemon_installer.bash from your shell and follow the prompts.
It will check for dependencies.
To add a friend you and your friend must BOTH export and send your identity bloqs to one another.
And then you and your friend must BOTH import each others identity bloqs and wait for the nodes to sync with each other.

Feature list:
 - Persistent recoverable digital identity
 - Small world network topology
 - Key management system
 - Kudos - a fungible and transferable reputation system
 - Sovereign identity
 - Web of trust
 - Rich command line interface (cli)
 - Feature rich text user interface (gui)
 - Data backups
 - Friend requests for friends of friends
 - Relay messaging
 - Secret sharing framework
 - Serverless architecture
 - Extensible protocol - build apps on Eudaemon small world graph using custom bloqs

Release notes:

This is a proof of concept!
Built on Linux, tested some time ago on Freebsd. Has not been tested on macos and windows.

Vulnerabilities:
 - There certainly are many - however Eudaemon allows the forming of secure private small world networks.
 - We are unaware of any way to attack the network externally.
 - Known attack vectors are limited to attacks from nodes that you have explicitly trusted - your friends.
 - So if you want to play with the proof of concept only add people you actually trust to your private network.
 - So save your seed phrases and critical backups at your own risk! - wait until we move out of proof of concept phase.
 - Very little to no validation of input content.
 
Incomplete and will be patched in later:
 - We have made every effort to design the bloqs in a complete a future proof manner, however if we discover an oversight we may have to reboot the chains (rewrite)
 - We did not have time to overhaul the TUI before launch - many of the features are hidden too many hops deep into the interface.
 - Drop bloqs not complete
 - Re-mapping guardians requires drop bloq functionality, so you wont be able to re-map your guardians after you select them until the next patch
 - Re hiding secrets after recovering them also depends on drop bloqs
 - CLI will certainly be changed to be more UNIX standard compliant
 - Formalised consensus framework for forming consensus
 - The system already allows for uploading a will and testament and splits your legacy private key amongst your guardians. However the interface and mechanism to form consensus of death and restore the legacy key for reading of will is not yet implemented. It works now - but would require some manual effort on behalf of the guardians.
 - Highly under-optimised!! Speed of deamon should be able to go up 5x just on simple optimisations of moving more variables into memory and implementing indexes on the database.

Thank you to all the family and friends for the support!

Thank you to all the dependencies that made this possible:
 - Bash
 - GNU userland
 - GPG
 - Syncthing
 - and many many more
 - Please consider donating to any of these great projects

Donations

If we get enough funds we will rewrite the system in Rust or Go...

BTC
bc1q4zx9gdvza79camsd90963j59ke7r4e9jl90alw
XMR
8BxusEYuoNLc3DpF4wfxJhRrcPbtZnW8DaDcwbCDKebdLd1YLxbhj9sPrwj1GfKG3QG17qCiARxtXVe ipNsfrGchMRCA32j
ETH
0xaaa389469fe5c7fd3a21a2801ffa94c7f703fc25
BSV
1D4oBJAU6k2wHLjivF1rDWQ5yMrrryAMto

It has been a very long time in stealth mode. We hope this system is of use! We look forward to collaboration and feedback!
-----BEGIN PGP SIGNATURE-----

iNUEARYKAH0WIQTG4Q0O8gGexag2Bp4o2BmaLTDCjQUCZEAaIl8UgAAAAAAuAChp
c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0QzZF
MTBEMEVGMjAxOUVDNUE4MzYwNjlFMjhEODE5OUEyRDMwQzI4RAAKCRAo2BmaLTDC
jdr1AQDeoAhZ5hb8o4lUd1Tbglu9E/x3aj1IULKnGIi4nK+U/AEAlMBPzGVu6YUO
/M75Yja3B3aOacUcYw51i1fcus3+uAQ=
=3YDf
-----END PGP SIGNATURE-----

reserved for updates

UPDATE:
There is also a conversation happening on the cryptography mailing list:
https://www.metzdowd.com/pipermail/cryptography/2023-April/038142.html

reserved! sound amazing!

Created new identity:

Please wait, identity creation can take up to ~ 10 seconds.

and after 10 seconds nothing happened

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

You are the first I am aware of, whom I do not know, to have executed the code. How exciting!

Remember Proof Of Concept, there are still bugs.

Ideally I would like to move issue tracking to https://codeberg.org/agathos/Eudaemon/issues

Having said that I will attempt to help diagnose the problem here.

We have tested on recent versions of Fedora, Debian, Ubuntu, Arch, Alpine and some time ago FreeBSD.


Debugging guide:

1)

Check the content of .eud/error_log

Your .eud/ folder, which we refer to as the eud_home, will be in your linux homedir within whatever name you gave your Eudaemon at install time.
eg ~/Calcifer/.eud/

2)

There is a deep bug with syncthing that will occasionally cause eud to hang on identity creation, this seems to happen 1 in 50 times or so - it is possibly due to port conflicts.
Many many hours have been spent trying to isolate this bug but it is still there...
Try running the installer again and if it still hangs on identity creation try next step.

3)

Open two terminal windows side by side (I like tmux for this).
In the first window make sure the Eudaemon is stopped.
The cli program is .eud/bin/eud-cli.bash
If you enabled alias bindings at install time then you can just type eud-cli stop , otherwise specify the full command .eud/bin/eud-cli.bash stop
Next start the Eudaemon in verbose logging debug mode. eud-cli -vld start

Now in the second window run the eud-tui and follow the prompts to create identity again.
If it errors out you will see the full error trace in the first window.

The full log will also be saved at .eud/sys_log

Be careful publishing contenct from the sys_log, it may contain private keys as well as the clear text content of your bloqs.
-----BEGIN PGP SIGNATURE-----

iNUEARYKAH0WIQTG4Q0O8gGexag2Bp4o2BmaLTDCjQUCZEP7MV8UgAAAAAAuAChp
c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0QzZF
MTBEMEVGMjAxOUVDNUE4MzYwNjlFMjhEODE5OUEyRDMwQzI4RAAKCRAo2BmaLTDC
jW23AQDVjgVE0KKITe3VciU8Es83x49rGvK/Y/AcbHwkgXiQ5AEA34D4/h+RIbX3
lXpHk+NgHLV6+uX9iKuHVicldt7qNw4=
=HhWM
-----END PGP SIGNATURE-----

I too got the similar issue of screen just mention wait 10 sec.
Also is there some sort of mining and coin generation part of this ?

Have created an identity already! Need friends to be added for this new journey ;D

Still reading the whitepaper for understanding the concept!

Best!

Did you look at the debugging guide above?

What OS are you running?

For the economic model and "mining" information check the Kudos section of the whitepaper at https://eud.ninja

Great! Let me know how it goes.

Hello, I'm from China. I saw the file you posted. But I don't know how to run it? I know some basic Ubantu systems

Hi! It has worked with chat function! Shows some warning relating to GBus as my linux box is text-based only.

Could I exchange ID with you ?
Or, can you create a chat channels within eud, so it is more easy to join and explore the network ?
Cheer!

Download and run:
https://codeberg.org/agathos/Eudaemon/src/branch/main/releases/Eudaemon_installer.bash

Hey how we can add us as a friends ? Its asking me for some file

"To add a friend you and your friend must BOTH export and send your identity bloqs to one another.
And then you and your friend must BOTH import each others identity bloqs and wait for the nodes to sync with each other."

How I can export identity bloqs ?
does that are an genesis.bloq ??

Or maybe we can exchange our ID ?

Hi,

In TUI `./eud-tui`, type key `p` to go into Profile. then type key `e` to Export identity bloq - for connecting with others. It will export a BLOQ file name `[YOURNAME]IDNO.bloq` in your home folder. Send that file to your friend.

In your friend side, after run TUI `./eud-tui`, type key `f` to go into Friends, then type key `a` to Add friend, then type key `f` to Import a friend, next is select the BLOQ file received from you to import, and follows steps.

Your friend has to export and send BLOQ file to you, and you do import that file as well.

Best!

Great thanks for explanation here is my file :
https://transfer.sh/GRfOqv/JustMineItIDNO.bloq you can get it with wget

can you send me your ID by transfer.sh website ? also anyone who want to do it ?

Here it is https://transfer.sh/meOfS0/f04everIDNO.bloq
Let a try!
Best!

Hallo,

Just report there warning appear on my terminal (i use text mode) for each received chat message, like below.

I did install all dependencies

Best

I will also try today. Looks nice.

ok so send me Your ID too

How do I add my server as an Device as I cant open syncthing as it need to use 127.0.0.1 address instead of my machine IP ?
On my main local node added ID of my second Device but can add it on my hosted remote one, any advice ?
Also does My hosted works like backup will keep my node working all time even if my local is off ?

and can you get my ID from https://transfer.sh/GRfOqv/JustMineItIDNO.bloq

and upload yours so I can be with contact with you on the EUD ?

Can you make an discord channel for quicker communication ?
I think is nessesary to get more contributors and donors to rewrite project in rust or go lang and then maybe we should focus on GUI wallet for windows as idea is really great but we need to allow simple users to join it and use and not all have some primary skills to run it on ubuntu or other linux system.

Firstly never mess with the settings in syncthing gui - it is there purely for debug viewing. If you changed any settings there you should:
n) Refresh network
and
i) Reinitialise network
from the main menu. Syncthing is fully managed by the eudaemon.

Multi device does work but it does not yet conform exactly to the protocol specification. New devices should create a discrete device key. Currently any additional devices added will use the same device key. They already properly create independent fresh syncthing transport keys at least..

Your first device will be your master device. Any additional devices added will be set to "slave / follow" mode where they cannot form bloqs, however they will propagate your new bloqs created by your master device and collect messages from your peers - AND propagate their bloqs as well. So you will be helping all your friends when you make your second device an always on server.

If you re-enable lines 207 and 529 in eud-tui.bash then you will have the options to add multiple devices.
      #echo "a) Add this device to an existing identity" #TODO re-enable in version 2 - currently too unstable
      #echo "a) Add device - add additional devices that you control." #TODO re-enable in version 2 - currently too unstable

I did re-stabilise the code before launch - it is working fine. I left in disabled because it does not perfectly reflect the protocol specification.

Hello,

My Kukos balance is negative now

Is that normal ?

Does daemin need any specified ports to be open for nice communication between nodes ?

$ ./Eudaemon_installer.bash
You need bash, zip and gpg to install Eudaemon, please install first
I downloaded Git using Windows

Then search for the tutorial and follow the prompts. However, I downloaded the ZIP installation package online, but I don't know much about programming. Can you teach me

OK  解决了
 but

Some MANDATORY dependencies are missing:
** python3 sqlite3 syncthing vifm jq pgrep pkill ssss-split ssss-combine inotify
 

I have already experimented for everyone, and even installation cannot be completed without a programming foundation.

I hope there is a telegram for communication telling me how to install and excavate

Here is my-

https://transfer.sh/oBJ3Ks/RichmanIDNO.bloq

I have added two friends
JustMineIt
F04ever


Now what can try at this stage?

Update: I did send few messages. Can you guys see?

Sorry chinagump, as per the release notes this is a proof-of-concept - it is a demonstration that the protocol is possible that has known bugs and and is not intended to run as a production system.

From the release notes in the original post:
This is a proof of concept!
Built on Linux, tested some time ago on Freebsd. Has not been tested on macos and windows.

It should work on linux subsystem for windows - but I have never tried it on windows.

If you use ubuntu on linux subsystem for windows it should allow you to resolve all the mandatory dependencies automatically.

This is certainly not normal.

Perhaps you could share the steps you took to get to that point? It could be a clock problem on your machine as kudos is linked to time.
What OS are you on?

This is purely related to syncthing which is the transport layer that Eudaemon currently uses. It generally works well out of the box with no configuration. It will use syncthing's public relays and discovery system.
Syncthing port information:
https://docs.syncthing.net/users/firewall.html
Discussion on syncthing NAT hole punching turn and stun:
https://forum.syncthing.net/t/a-few-questions-about-quic-hole-punching-and-stun/16490

* Your kudos balance is: -46,739,860 Kudos

I am on Ubuntu 22.04.2 LTS. Time synced well. Steps as below:
- Install dependencies and Eudaemon.
- Create my identity.
- Add friends: two friends.
- A day after that, Kudos balance is about 1xxx, I dont remember exactly.
- I try to send some kusos to friends, but It gives error that i need the balance must greater than amount to be sent.
- I found that my balance is negative, about 20,xxx,xxx Kudos.
- A day after that I try some times Refresh network (n), and Reinitialise network (i). The balance went back to zero.
- Try to send kudos again, error, balance went as double negavtive -46,739,860 Kudos. Now it is -46,738,918 Kudos. Looks increasing.

What should I do next?
Should I create a new Id?

Thank you and Best!

How to read unread bloqs?
I don't see any option .

You can:
1. Check unread messages in chat (c) or in broadcasting (b)
2. Check bloqs in Notifications (v), and can mark it as read.

That is as I do

Best!

Hey Y'all,

This looks very promising!!

One thing only irks me up quite a lot: The tones the daemon produces from time to time.

So, I have to ask: WHY? Cuz it's pretty annoying when you're in the middle of a video you're watching, and the tones pop up to ruin your enjoyment of said video?

So, fine peeps from EU, what gives?! :)

Cheers,
Gus

Thanks. Working for me now.

Added You as a friend :)

Ok so as you said Syncthing is just for debug and better to not do anything there what if I get a loot of messegaes that others want to share some folders :

motions wants to share folder "JustMineIt mempool" (6524844D6D045FDB5AF52713B5AF9B3225078F93mempool). Share this folder?

RichManUbuntu wants to share folder "motions mempool" (FCD2DBD62FC64E8C4C7AD2833E5E5A787A726327mempool). Add new folder?

plateau wants to share folder "motions mempool" (FCD2DBD62FC64E8C4C7AD2833E5E5A787A726327mempool). Add new folder?

motions wants to share folder "motions mempool" (FCD2DBD62FC64E8C4C7AD2833E5E5A787A726327mempool). Add new folder?

con1 wants to share folder "motions mempool" (FCD2DBD62FC64E8C4C7AD2833E5E5A787A726327mempool). Add new folder?

There is option to add but the folder field is empty should I just ignore that messages or add those folders ? and leave Syncthing  without a touch

Drop Your ID and I will send my own too so we can be a friends

Ha cool! These are all people wanting to be your friend. They have imported and verified your identity bloq.

In order to complete the pairing you need to also add them as a friend in the eud menu which will lead you to import their identity bloqs.

This is because the idenity bloq contains the friend's public key. You need that to do a complete connection on the protocol. If you just accept their syncthing connection via the syncthing gui nothing will work - you may even break your node...

I will post my identity bloq in the near future and join in the fun....

I appreciate your intention to support, thank you!

My concerns with moving comms over to discord is:
1) I would rather use something aligned with the priciples of free software
2) I would prefer protocol explanations and discussion to be somewhere publicly discoverable so new people can follow the conversation

I'm considering forming a mailing group and also possibly writing a nostr plugin for eud so that we can move discussions to naitive Eudaemon and still expose the conversation for public reading.

These are sound notifications of newly arriving bloqs being processed. I intend to expose a cli call in the next release to turn sound on or off. I also would like to make a nicer set of tones that correspond to differnt bloq_type - they are not so musical at the moment...

Maybe someone wants to help write that and submit a pull request at https://codeberg.org/agathos/Eudaemon/

The thing is they are already my friends mean most of them but syncthing shows that asks

no go for me to generate identity my log:
Failure exit code: 1 at line 638: play -n -c1 synth sin %-12 sin %-$sound sin %-$sound sin %-$sound fade h 0.1 1 0.1 2> /dev/null: /root/reb0rn/.eud/bin/eud_lib.bash

screen where is node running:
curl: (7) Failed to connect to 127.0.0.1 port 55796: Connection refused
++ printf '\''%s\n'\'' fail
fail'
+ [[ ++ printf '%s\n' 'pinging transport layer'
+++ printf '%s\n' 'header = "X-API-Key: cPRUrjkV92ibfWa9SUxVpy6F3TugWny7"'
+++ get_device_api_address
+++ sqlite3 /root/reb0rn/.eud/db/eud.sqlite 'SELECT api_address FROM device where isme=1;'
++ curl -f -X GET -K /dev/fd/63 127.0.0.1:55796/rest/system/ping
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (7) Failed to connect to 127.0.0.1 port 55796: Connection refused
++ printf '%s\n' fail
fail == *\p\o\n\g* ]]
+ false
+ sleep 1


UPDATE
On different VPS it worked fine

VPS1 which did not work is 20.04
VPS2 is 22.04 which work

This is my bloq:
https://transfer.sh/utefe2/reb0rnIDNO.bloq

Hey eudaemonia,


AH-HA, this explains a lot and thank you for considering the on/off button on them :)

Thanks for your efforts. This is looking promising and should replace Keybase in no time if adoption continues to grow, right?

Cheers,
Gus

Hello,

How to stop the eud services properly as there are lots of background services running.
Just want to test how to stop and start manually without any issues.

can anyone make an discord unofficial one for better communication ?

I stop it with q (quit)
and close my pc no problems till now

eud-cli stop

you can also eud-cli enable and eud-cli disable to enable/disable it as an actual deamon / system service if you are using a system with systemd. This is so it will start automatically on boot. See code below extracted from eud-cli.bash:

                        status)
                                systemctl --user status "$eudaemon_name"".service"
                                ;;
                        start)
                                systemctl --user start "$eudaemon_name"".service"
                                ;;
                        stop)
                                systemctl --user stop "$eudaemon_name"".service"
                                ;;
                        enable)
                                systemctl --user enable "$eudaemon_name"".service"
                                ;;
                        disable)
                                systemctl --user disable "$eudaemon_name"".service"
                                ;;
                        daemonise)
                                mkdir -p ~/.config/systemd/user/
cat <<EOF > ~/.config/systemd/user/"$eudaemon_name"".service"
[Unit]
Description=$eudaemon_name the eudaemon
After=network.target

[Service]
Type=simple
ExecStart=%h/$eudaemon_name/.eud/bin/eud-cli.bash start
ExecStop=%h/$eudaemon_name/.eud/bin/eud-cli.bash stop
RemainAfterExit=true

[Install]
WantedBy=default.target
                               
EOF

Thanks. These commands works perfectly.

I made a community discord let see how it goes

https://discord.gg/2YFmrBRkuq

How to create a proper backup of Kudos wallet?

https://transfer.sh/1CIxYe/rajkamalIDNO.bloq  add me

The best way to backup your identity is by selecting guardians under the backup identity option under your profile menu. This uses threshold cryptography implemented in Sharmir's Secret Sharing System. It requires that you have at least two trusted peers that know you personally and can verify you in the event of your identity loss and recovery process.

Kudos is derived from your identity - there is no separate key to be backed up. As long as your identity is backup up your kudos is also then backed up.

Finding reliable identities at this stage can be difficult, what is the proper way to do a self backup and save my identity?

The purpose of the proof of concept is to demonstrate how to have a scalable identity system and social network that has no central authority and also does not need manual backups of keys / seed phrases. The audience here probably has no problem backing up keys - however for an architecture to succeed at scale it must have socially intuitive recovery methodologies. Those models are the hard ones to build - this is the novel innovation.

I have not built an interface for manual backup, though I do intend to add this, it is fairly simple and there are a few possible ways to implement it. You basically need to backup your identity private key which unlocks your bloq 0, which is your genesis bloq. Then you get a copy of your chain from one of your peers and use your ID private key to open your chain and replay your chain to deterministically rebuild your state. You could also just make occasional backups of your .eud/ folder - this is a sufficient backup, however if you restored from an old .eud/ backup you would have to manually set your eudaemon to not form any bloqs until it has fully caught up with bloqs that were formed since the backup was saved. This is easy to automate, but has not yet been implemented.

If you do not have two real trusted peers then the next most "proper" way currently would be to just create another eudaemon and pair it to your identity. If you loose your primary eudaemon then your secondary eudaemon can be set to primary and then can start forming bloqs and continue your chain.

I hope this is helpful?

When I install on Ubuntu 20, it gives me error cannot connect after installing and following all steps.
Any fix for this?

I have heard that Ubuntu 20 does not work, I will try to ascertain the source of the problem in the coming weeks.

Can you upgrade to 22.04?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Ok I will join the fun here, sorry it has taken me this long, I've been hesitant to join as Eudaemon was designed to used to create networks of trust - not connect strangers. However in the context of a test-network actually I think this can be quite useful.

Rules of the game (rules for me anyway).

I am considering this a test-network for the purpose of testing the system and discussion of the protocol architecture and the implementation. As the live network is expected to be based on actual trust connections, that is people you know, not strangers. Though this may be a nice way to make some friends.

I will not be using my Agathian keys - though I will sign this message as an assertion of the validity of this test-network identity bloq and message.

I will favour broadcast over direct messages. If I broadcast a message that is a response to some other persons broadcast then I will attempt to encode the content of the question within the response.

Anything that I broadcast I will possibly pipe to some other system so that it is publicly readable.

Remember the content from the release notes:
- -------------------------
Vulnerabilities:
 - There certainly are many - however Eudaemon allows the forming of secure private small world networks.
 - We are unaware of any way to attack the network externally.
 - Known attack vectors are limited to attacks from nodes that you have explicitly trusted - your friends.
 - So if you want to play with the proof of concept only add people you actually trust to your private network.
 - So save your seed phrases and critical backups at your own risk! - wait until we move out of proof of concept phase.
 - Very little to no validation of input content.
- -------------------------

I ask you kindly not to attack my node, we can spin up a adversarial network at some point in the future to look for security vulnerabilities.

I will not be storing any important data under this testing identity.

If I stop using this testing identity at some point in the future I will sign a message here in this forum invalidating this testing identity.

So who wants to be friends?

https://transfer.sh/aTdil9/Agathos_testnet_1INDO.bloq

Start of file Identity bloq with filename 'Agathos testnet 1IDNO.bloq'

- ------------------------------------------------------------------------------------------------------------------

- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

{"id_type":"IDNO","adr":"SLO4O5L-YAJYHIM-7ODKBTE-6TDHITC-CML5HWP-747AMR2-37P36YS-RATMRAG","name_64":"QWdhdGhvcwp0ZXN0bmV0CjEK","proto":"st"}
- - -----BEGIN PGP PUBLIC KEY BLOCK-----

mDMEZFpiYxYJKwYBBAHaRw8BAQdANrjXFQyQomYviH8juWhbV5ghPeyMxfi+8goa
7AoMzny0FFRkaXFPSHBHR1huaXFUS1lMVWZ3iJAEExYIADgWIQSB7xPns+pn6kIR
9KqI1wQZLTllRAUCZFpiYwIbIwULCQgHAgYVCgkICwIEFgIDAQIeAQIXgAAKCRCI
1wQZLTllRB7JAQDyO6yojUQnMm4h9JNc8p/9GhygEftCv6eYEoKJ7KemNAD+KH7F
6qAAXtjBrwZ9cIm4hJrYtkQMf77O5+dRt6AIwwG4OARkWmJjEgorBgEEAZdVAQUB
AQdAMJjORt5/JdJNceYUujqmly/hXTl8P+GTE94oggU5ADcDAQgHiHgEGBYIACAW
IQSB7xPns+pn6kIR9KqI1wQZLTllRAUCZFpiYwIbDAAKCRCI1wQZLTllRD5cAP41
Njt2X1YNUrla49IdSsS2UqgJ1nXxOEPYA24hECXCyQEAyuU78nhfeK12yDqSR2Pu
+LYi2pTWUT7owLbEE7V7hgE=
=hAAB
- - -----END PGP PUBLIC KEY BLOCK-----
- -----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQSB7xPns+pn6kIR9KqI1wQZLTllRAUCZFpidwAKCRCI1wQZLTll
RJ+FAQD7BmeKi6VBUTrLq2PjlGdbCkOfG7YemjJaydq3hrRBwQD+Iu5vDHr0vtFy
7BsnyGiWBjB1gvgKzw6l+vGoWPOnGwI=
=GZ7w
- -----END PGP SIGNATURE-----

- ------------------------------------------------------------------------------------------------------------------
end of id bloq file


-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQTG4Q0O8gGexag2Bp4o2BmaLTDCjQUCZFpq1wAKCRAo2BmaLTDC
jVwiAQDPwjwo2KKsUv7wQXybhZ7g68/uSi+r568pTPdivY9jDgEA9FpSub5eS/ZA
iCqku+RwQhrvAVQNQtCh2kalhQkQSAs=
=blUR
-----END PGP SIGNATURE-----
~                                                                                                                                                                                                                                                                                                                                                                      
~                                                                                                                                                                                                                                                                                                                                                                      
~                                                                                                                  

Reserved for updates relating to this testing network instance

Hello  @eudaemonia,
We have found the protocol and the idea very interesting. We believe we might apply it into our project.
After internal discussion we decided we want to help with the development of Eudaemon.
So question for you, are there any known issues, or feature requests that we can help you with?
Is there any roadmap for the project?
We can also help with rewriting in Rust.

Looking forward for your answer.

Go into the Discord, you can talk to developer there:

https://discord.gg/2YFmrBRkuq