stackzero

looks high lev

you're right- and it's sharp

Is there an ELI5?

Change the name to something short that sounds like it can be part of my stack and existed in linux forever e.g. ert Earthly sounds too mid 2010s and something extra/startupy

Please roast this simple order book implementation

+1 for 51% font attack

bitcoin maximalism is the worst. wealth will tend to concentrate over time anyway (parteo distribution) and a "ruling class" will emerge on bitcoin. miner's voting with hash power is not the future of cryptocurrency governance. If bitcoin does not evolve to allow this effectively it will be regulated out of common use.

It's possible to experiment and build decentralized governance models directly into blockchains see e.g. https://polkadot.network/polkadot-governance/ (disclaimer not a shill I like the tech)

Unfortunately, this is a 2015 take on blockchain. Protocols are now to the point where you can have the ability to create "courts" and social governance protocols on the network itself to resolve this kind of thing, also see: https://vitalik.ca/general/2021/03/23/legitimacy.html

Good luck, we'd be lucky to have you :)

Centrality | Auckland | Onsite (or remote NZ)

Building decentralized ledger technology with rust + wasm.

Our team comes from various programming backgrounds python,c++,java embedded, enterprise, data science. If learning rust, distributed systems, or pushing the boundaries in an emerging industry sound fun then please reach out!

We're looking for:

- Senior Fullstack

- Senior Rust Dev

- Intermediate Rust Dev

apply here: https://centrality.ai/careers/ or email: peopleops(at)centrality(dot)ai

if you want to know more, drop me a line: beauchjord(at)gmail(dot)com

cryptocurreny != investment scam. It's just another way to transfer and store value.

Interacting with automated contracts is an interesting extension to that system which can make things alot more complex.

The 'dark forest' comes from a kind of man-in-the-middle attack where anyone can see the order book and exploit it, by putting their own slightly better orders in. Hence the need for co-operation with a closed order book (miner) to get the transaction in safely.

gg man. Really enjoyed your posts since starting rust.

is this like twitch plays pokemon?

RIP. His book "Debt: The first 5000 years" really impacted my thinking about how our economy works and how I might help it in the future.

Accurate IMO. You can get the components or organs but they don't snap together, more careful integration required...like surgery

As someone not from a js background, when would I use this? is it a drop in replacement for node with TS support? or something else

+1 enjoyed how accessible this write up was

I'm interested in pointers on this in general, not just wrt the current climate.

There's some good wisdom in this story. It reminds me of that article posted here about a more page cache efficient b-trees vs. Knuth's theoretically ideal version

- You can't lead a team further than you have been yourself There is a constant need to spend time up-skilling, performing tech spikes, thinking ahead - 20% of people do 80% of the work. You should be in the 20% and also invest time with the people in your team that are in the 20% - Genuinely care about the people you lead and help them get better at whatever their goals are

Some quickfire help:

- Agree on a team policy for code reviews, formatting, style, etc. (this alone should eliminate most of the subjectivity)

- Read and share this https://google.github.io/eng-practices/review/ with the team

- Design discussions could be agreed on before code is written

Poor guy, writing code for fun and maintaining an OSS project long term aren't the same thing. Nor do they require the same skill set.

With abit of elbow grease we can pick the project up again, "reputational damage" is not the end https://en.wikipedia.org/wiki/Service_recovery_paradox

I want more articles like this.

>In general, reviewers should favor approving a CL once it is in a state where it definitely improves the overall code health of the system being worked on, even if the CL isn’t perfect.

This is a great rule of thumb

Centrality.ai | Blockchain Engineers | New Zealand | ONSITE

We're a blockchain venture studio based in Auckland, New Zealand. Looking for engineers to help build out our core blockchain infrastructure on Substrate.

If writing rust for your day job, building decentralized protocols for the web 3.0, wasm virtual machines and byte code interpreters sounds like a) not gibberish and b) awesome then reach out.

Rust experience or interest to learn with some serious experience in systems level programming e.g. C/C++.

Other pros would be knowledge of cryptography, web assembly, or DLT in general.

Oh there's also Kombucha on tap and chief dog officers if you like that kind of thing.

Reach out: peopleops(at)centrality(dot)ai

Scanned the paper and looks like they're using keys that are < 256-bit hence the vulnerability. Also I think the encryption keys which were found vulnerable are separate from the transaction signing keys

I think this reflects the enterprise culture and auditing practices more than anything

Don't ask "will you mentor me?" just ask a specific question and you've got a mentor