The computer driven markets for instruments like stocks and exchange traded stock options, have transformed finance and the flow of capital. These markets are enabled by order matching engines (and the infrastructure that supports this software). Before computer trading networks and matching engines, stocks where traded on cavernous exchange floors and transaction costs where high. When electronic trading fully matured, floor traders were a fading anachronism and transaction costs had been reduced to pennies a share in many cases. Electronic trading could not exist without advanced network infrastructure, but without the software matching engines no shares would change hands. The computer trading networks, the matching engine software has also created a concentrated nexus of potential failure. Failures in these systems have increased as the frequency and volume on the electronic networks has increased. The position of order matching engines in the trading infrastructure makes these systems o
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| { | |
| "title": "Mainnet dummy upgrade", | |
| "description": "This is a dummy proposal for testing governance flows, the urls below are meaningless for nw.", | |
| "source_code_url": "https://github.com/aptos-foundation/mainnet-proposals/blob/main/sources/2023-06-05-reenable-signature-checker-v2", | |
| "discussion_url": "https://github.com/aptos-foundation/mainnet-proposals/issues/28" | |
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| //install react-app-rewired and all the broswerify packages | |
| const webpack = require('webpack'); | |
| module.exports = function override(config) { | |
| const fallback = config.resolve.fallback || {}; | |
| Object.assign(fallback, { | |
| "crypto": require.resolve("crypto-browserify"), | |
| "stream": require.resolve("stream-browserify"), | |
| "assert": require.resolve("assert"), | |
| "http": require.resolve("stream-http"), |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| package main | |
| import ( | |
| "fmt" | |
| "log" | |
| "net/http" | |
| "os" | |
| "github.com/gorilla/websocket" | |
| ) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| useful when testing lamdas for s3 buckets | |
| { | |
| "Records":[ | |
| { | |
| "eventVersion":"2.2", | |
| "eventSource":"aws:s3", | |
| "awsRegion":"us-west-2", | |
| "eventTime":"The time, in ISO-8601 format, for example, 1970-01-01T00:00:00.000Z, when Amazon S3 finished processing the request", | |
| "eventName":"event-type", |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| //client-side code | |
| const formik = useFormik({ | |
| initialValues: { | |
| username: '', | |
| bio: '', | |
| img: '' | |
| }, | |
| onSubmit: async (values) => { | |
| let data = new FormData(); |