Yggdrasil

eu.neilalexander.yggdrasil
by Zapstore _@zapstore.dev

Official implementation for connecting to the Yggdrasil Network from Android

Republished from GitHub / F-Droid by the Zapstore main account.

Yggdrasil is an early-stage implementation of a fully end-to-end encrypted IPv6 network. It is lightweight, self-arranging, supported on multiple platforms and allows pretty much any IPv6-capable application to communicate securely with other Yggdrasil nodes. Yggdrasil does not require you to have IPv6 Internet connectivity - it also works over IPv4. This app allows you to connect to Yggdrasil Network and use any service located in this network. It works as VPN service, but all your usual traffic will go trough your provider, not through Yggdrasil Network. Also, it is not a goal of the Yggdrasil project to provide anonymity. Direct peers over the Internet will be able to see your IP address and may be able to use this information to determine your location or identity. Multicast-discovered peerings on the same network will typically expose your device MAC address. Other nodes on the network may be able to discern some information about which nodes you are peered with. All traffic sent across the Yggdrasil network is encrypted end-to-end. Assuming that our crypto is solid, it cannot be decrypted or read by any intermediate nodes, and can only be decrypted by the recipient for which it was intended. However, please note that Yggdrasil has not been officially externally audited.

First release: Jan 8, 2025, 2 total releases.

Most recent release: Mar 13, 2026.

Repo

Appears in 3 app stacks.

0 sats / 0 zaps received in the past year.

Sats Received

Underlying data available via MCP: app_zaps, app_releases.

Zap Count

Underlying data available via MCP: app_zaps, app_releases.

Releases

  • Mar 13, 2026 0.1-021
    Updated core library to 0.5.13. Added peer validation on input.
  • Jan 8, 2025 0.1-020
    Updated core library to 0.5.12, presenting these changes: ## Changed - The parent selection algorithm now only chooses a new parent if there is a larger cost benefit to doing so, which should help to stabilise the tree - The bloom filters are now repropagated periodically, to avoid nodes getting stuck with bad state - Minor tweaks to the routing algorithm: - The next-hop selection will now prefer shorter paths when the costed distance is otherwise equal, tiebreaking on peering uptime to fall back to more stable paths - Link cost calculations have been smoothed out, making the costs less sensitive to sudden spikes in latency - Reusable name lookup and peer connection logic across different peering types for more consistent behaviour
    More…
    - Some comments in the configuration file have been revised for clarity - Upgrade dependencies ## Fixed - A memory leak caused by missed cleanup of the peer response map has been fixed - Other bug fixes with bloom filter propagation for off-tree filters and zero vs one bits - TLS-based peering connections now support TLS 1.2 again ## Fixes in Android app * Made some UI improvements * Updated some dependencies