Gena

🦖🦕 Generational evolution in stock trading be like: 🧓 Grandpa: "Operator, put me through to Wall Street." 👨 Dad: "Just submitted my order—settles in 3 days." 🧑 Me: "Swapped $NVDAx on @Solana in 3 seconds with @xStocksFi." Welcome to the future with Solana, lads!

Pepembrian came to @token2049 🐸🐚🇦🇪

gm from @SolanaCrossroad with @gena_with_beard @cambrianone

Hey, frens. I recently talked with TechBullion about current market situation around Restaking👌 Feel free to jump and read! techbullion.com/restaking-is-h…

1/4 🏆🪄Cambrian Hack Winners After a month-long competition and careful judging, these projects have demonstrated exceptional innovation using our platform: 1st Ping Network @PingNetwork_io 2nd Ant Vault @wanaokii 3rd STABLE-FUNDS @Ge0frey_ 🧵...

It was our great pleasure and honor to run the first Cambrian hackathon at Solana APEX in cape Town. Big thanks to the orgs and the dev teams! 🤝 🇿🇦

At Solana Apex Capetown

This year the sunrise of restaking is about to come to Solana with the help of @cambrianone 🤝

Recently found out the there is no example of how do a raydium swap in python. Welp, now there is one gist.github.com/egv/b2fa88e1c6… Use at your own risk

Got so frustrated with presentation-making software that I decided to create our new pitch deck through code. Stay tuned for the first open-source pitch deck ever made.

Solana. That's it. That's the tweet.

Soon

@calilyliu and we at @cambrianone are building all the needed tooling for that to happen nice and easy

I guess I am more interested in how tradfi becomes a solana L2

ethereum rhymes with nokia

Mos def

@gena_with_beard participated in an exciting AMA on August 7 hosted by @artnauka in the RestakingModularity TG community and we present AMA Recap with interesting questions and answers! We would like to thank all the participants - @dariaagad, @0xkenjiii and @artnauka for a very engaging discussion about restaking and modularity in the Solana world! Let's dive into it 👇 cambrianone.substack.com/p/ama-recap-so…

Orchestration problem in restaking Compared to staking, restaking introduced a third party to the PoS consensus — AVSes, increasing the number of actors in the process to more than two. And they all need to play in perfect harmony with each other to get the best out of the process. In music, even small orchestras need conductors to be in sync and sound glorious, and for CambrianOL's restaking, one such conductor will be. Let’s specify the problems that each of the parties has in the restaking, and try to find a unified modular way to solve them. Restaking legend by @galaxyhq 1⃣ Let us first take a look at restakers. They want to optimize their stake according to one or more parameters, e.g. risk profile or return per stake, or they want to back specific nodes that perform certain tasks. All you can do now is either allocate your stake manually or use curated vaults such as those offered by @mellowprotocol. Either way, these solutions are not very dynamic and require a lot of attention, either from the person recovering them or from a vault curator (or both, if you want to switch vaults). Another obvious solution is @symbioticfi, which also works with vaults as a coordination layer for restaking. Furthermore, the implementation of these solutions on Solana differs greatly from EVM-based solutions. 2⃣ Next in line are AVSes. These have some flexibility in choosing the nodes on which they perform their tasks, but even these are not very dynamic. And what if there are not enough nodes in the restaking layer they were originally intended to run on? What if they want to dynamically change their requirements dynamically to accommodate workload or other factors? Again, this can not be done very efficiently because there simply are not the tools to do it. 3⃣ And last but not least — worker nodes. This may look simple, but it's not really. Imagine you have set up your node, selected AVSes to run, set a stake on yourself or attracted another restaker’s stake, but your node is never selected for task execution. You can never know why, and that is really disappointing. Therefore, some statistics and simulation tools will certainly come in handy, as well as some simulation tools. In addition, such a solution will allow interaction with the different levels of restaking in Solana such as @Picasso_Network, @solayer_labs, @jito_labs and others, both on the restakers' side and on the operators' side. Definitely, some kind of conductor is required to make this orchestra play in perfect tune. Obviously, the solutions to all of these problems depend on the parameters of the nodes, which makes a good telemetry solution a must. We need to collect as much data as possible to make the best decision on restaking funds or delegating jobs to a certain node, as well as building analytics and simulations for node selection. Next, it is safe to assume that all solutions require the same data from all nodes. This data may also contain some aggregated values, such as the total bet between certain nodes, the place of the current node in the list with the most bets, etc. We can consider them as the result of a SQL query (sorry for the technical issues, this will happen again later) Once we have these query results for all nodes in the system at a given time, we need to find the required distribution of deployments and jobs across these nodes. The logs of this distribution can then be used as analysis tools for the nodes. As we have already found out, a worker node can be fully described by a set of values that we collect from it during our system work. The concept of orchestration is quite simple: we introduce a special function that receives this set of parameters and returns a deployment ratio for the given node, or 0/1, to see if a job should be run on a node or not. For now, you can think of this function as a Solana program. But how are we to know when to invoke this function? We will recalculate the distribution based on trigger events. These can be significant changes in node parameters, changes in AVS jobs, timers and general user events. All these triggers are placed in an asynchronous queue, which is then processed by the event manager, which throttles and groups all the triggers to minimize the workload and send the signal to the AVS orchestration to perform the required calculations. Subsequently, this AVS performs all the required heavy lifting, is validated and the results are again placed in another asynchronous queue to be processed by the change manager. This program receives the results of the orchestration calculations and transforms them into raw API calls to restaking layers to change their state to match the required state. This is a top level view of the orchestration solution. And this topic requires further in-depth research and search for answers to the following questions: 🟨 How the conductor function should be made. Are they real Solana programs or should they be written in some kind of DSL and be only stored on-chain? 🟨 What are those asynchronous queues that we use for calculations? Is it the blockchain itself, or is it something like Kafka or Zmq? 🟨 Where and how do we store nodes’ telemetry? On-chain or off-chain? If off chain then how do we prove it’s validity an authenticity? 📚 Read the full article on our Substack: cambrianone.substack.com/p/orchestratio…

New website is up, testnet deployment coming next, and soon

It’s alive! cambrian.one