aya VS docs

In my last article, I briefly explained starting a project with rust-aya, including using their scaffolding generator. If you need a refresher, feel free to revisit that article or check the rust-aya documentation.

The scaffolding provided by rust-aya includes everything we need to start building our program. By specifying the program type in the command, as we did with program_type=xdp, it sets up the necessary base for that specific type of program. For more detailed information on how all this works, it's a good idea to check out the documentation on the rust-aya website.

https://github.com/aya-rs/aya is very interesting, used to power this.

Would love to see the final results of this hacking in a git repo.

Now I'm back to learning about eBPF with the help of this great book by Liz Rice. I'm using libbpf-rs and converting the book examples into Rust (except for the actual bpf programs, which are in C, I have plans of coming back and converting everything to Rust with aya). If you're interested in eBPF stuff, and want to check out it with Rust here is my repo which could be helpful (almost every piece of code is commented).

In case anyone was wondering, the link to the Aya book towards the end of this post is wrong. It points you to:

https://aya-rs.dev/

Which has almost no content other than a spartan TOC. The actual book URL is here:

https://aya-rs.dev/book/

[GitHub - aya-rs/aya: Aya is an eBPF library for the Rust programming language, built with a focus on developer experience and operability.](https://github.com/aya-rs/aya) [GitHub - kentik/convis](https://github.com/kentik/convis) [Implement an eBPF decompiler/disassembler · Issue #838 · capstone-engine/capstone · GitHub](https://github.com/capstone-engine/capstone/issues/838)

The biggest difference is that it doesn't depend on or call into libbpf (pure Rust). The interface is also intended to make it really easy to manage lots of different probes that may or may not load across several kernel versions, so you can write-once-run-anywhere. The motivations are pretty similar to aya, but with a more limited feature set and emphasis on production stability across many kernels.

Use and contribute to Aya, an open source eBPF library for Rust https://github.com/aya-rs/aya

If anyone is interested in how Voldemort would store their crypto, he wrote a whitepaper explaining it five years ago.

Come over to the forum (https://forum.grin.mw/). Join our keybase (https://keybase.io/team/grincoin). Familiarize yourself with the concepts (https://github.com/mimblewimble/docs/wiki/A-Brief-History-of-MimbleWimble-White-Paper) and the code (https://github.com/mimblewimble/grin). Talk to the devs in keybase about what is needed, collaborate with them to find a good task that is interesting to you, useful to the project, and within your skill set to undertake. Finally post a bounty here (forum.grin.mw/c/bounties/) including milestones and desired compensation. If it gets approved, make the thing, get paid in bitcoin.

andytoshi (Poelstra) did not make the original mailing list post: https://github.com/mimblewimble/docs/wiki/A-Brief-History-of-MimbleWimble-White-Paper

It was supposed to mean that when the emissions schedule is a linear function, it is bound to have a heavy decline in the beginning. Here is something from the monetary policy docs: