Topic: Eudaemon: A peer-to-peer electronic identity system (Read 863 times)

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

https://discord.gg/2YFmrBRkuq

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.

Reserved for updates relating to this testing network instance

-----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-----
~                                                                                                                                                                                                                                                                                                                                                                      
~                                                                                                                                                                                                                                                                                                                                                                      
~                                                                                                                  

Can you upgrade to 22.04?

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

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

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?

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

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.

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

How to create a proper backup of Kudos wallet?

I made a community discord let see how it goes

https://discord.gg/2YFmrBRkuq

Thanks. These commands works perfectly.

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 < ~/.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

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

can anyone make an discord unofficial one for better communication ?

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.

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

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