This blog post discusses the design of the PAX ethereum smart contracts with an emphasis on our minimalist contract design philosophy.
Over the past few years, I’ve had the opportunity to build out a world-class engineering team at Paxos, a fintech startup on an ambitious mission to enable the movement of any asset at any time in a trustworthy way.
At Paxos, we’ve been running our services on Kubernetes for a while, but had trouble managing multiple environments until we adopted Helm and ChartMuseum.
Every software system requires an exhaustive amount of configuration and maintenance: from provisioning servers, deploying code, installing and upgrading services, to storing data, managing DNS records and applying security protocols, there is a tremendous amount to consider.
The main problem with (traditional) synchronous code, is that processes hang while waiting for external data.
In this series of articles, I’m aiming to give you a solid foundation for blockchain development.
For the last 15 years, I have predominantly worked on Distributed Systems of various size and complexity. Over the last couple of years, I have become
Getting into blockchain development can be pretty intimidating. There’s a whole host of weird terms that are thrown around like “coinbase” and “merkle root” that not only look odd, but are not obvious.
At Paxos, we give all software engineering candidates a short take-home test before deciding if we want to move forward with an in-person interview.
Many people across the technology and financial industries are dubbing blockchains as the greatest innovation since the Internet.
Although asset managers initially explored Bitcoin as a new investment opportunity, it is digital securities settlement infrastructure inspired by Bitcoin’s underlying technology, blockchain, that may have a greater impact on buy-side firms.