Skip to content

Instantly share code, notes, and snippets.

@staccDOTsol
Last active May 7, 2022 09:20
Show Gist options
  • Save staccDOTsol/a1ddf1389668b2743c9bccbe11c4f6ba to your computer and use it in GitHub Desktop.
Save staccDOTsol/a1ddf1389668b2743c9bccbe11c4f6ba to your computer and use it in GitHub Desktop.
this is soma; I still refuse to do a slidedeck

goodmorning solana

Solana does all of the things very wonderfully, and it's a shame that some low-hanging fruit from a susceptible chain has come under attac over the recent year or so

All that aside, we can offload some of the trauma & make Solana great again.

  1. we mirror solana state, trusting their consensus as gospel
  2. we write our own new testament; solana's people do not have to trust it. it doesn't matter.
  3. we write back to Solana what we choose, and if necessary do on & offchain magic to write it the way that is acceptable by solana --> gm, the discern000r stops here and goes 'how can you ensure it's in the same block.' There's some good theories here and we're open to suggestion (and smrter ppl to dissect the thing I realized in a dream && promptly forgot in another dream, like the grandpa mad scientist in Futurama) - the short answer is thus: more of the discerning ppl that mite appreciate the volumes and/or mite not appreciate any and all potential or sustained censorship (or threat/implication of/thereof) in the current l1 environment are more than welcome to exist here, barring (extensive) ab0000se... refer to mirroring programs, below, and mind you we'll do the work of mirroring the free and open source ones we decide are worthy :) notably we're going to financially & culturally incentivize ppl to opensource -everything- although not a requirement for the welcoming && hedging against potential censorship policy :)
  4. Soma starts writing blocks simultaneusly, on a separate ledger. To avoid confusion & the thing screaming at us we hash the bs58 blockhashes again, arbitrarily as base16 for now & to be cute we've prepended 0x.
  5. notably we can at time of writing support packets about 2.815x larger, in a single transaction. negligible effort brings this to about 7x.
  6. this is advantageous for a number of parties, notably a. anyone wanting larger transactions. b. solana as a whole, as the point of critical velocity is when solana validators realize we allow them to reroute traffic they don't want - imagine 4 failed candy machine mints in a row, on solport's fake candymachine? well, we redirect that and solana doesn't go down that day, our L2 batches them into one much larger transaction, fails them, and makes bank with the tx fee. thanks tom! c. idk. cool shit like 'mint 50 nfts at once' sounds like garbage and counterintuitive but all y'all are excited about fractionalizing nfts anyways, so if you don't get it then we can go opposite for you :) d. we're going to hydra everything from ground-up, including validator rewards. you're welcome. e. anyone doing mev benefits from doing it with us f. anyone who likes volume on their programs will want a mirror program with us, cuz of the kids in the previous point.
  7. that wasn't obvious, so read: it ain't about solport and busted cm, it's about --any validator who doesn't want the load of any transaction based on any trend--
  8. I haven't yet mentioned that while we do everything (much) bigger, we also do everything (much) faster with hardware designed specifically to execute shit. cpus and gpus be damned, it's like mining on those vs an ASIC :) I defer to narf for details.
  9. we charge an awful lot more for these bigger & faster tx. validators rejoice!
  10. yip
  11. assets will exist on both chains, those we want additional features for will be done as synthetic assets with 1:1 backing from a strataprotocol bonding curve with the sol asset

there's other cool shit I am forgetting

:)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment