0xPatrick 0xpatrickdev

Initial checks

Start by checking that there aren't any previous ssh keys inside the FIDO2 authenticator of your YubiKey. You can check if they exist by running the command below:

nix shell nixpkgs#yubikey-manager -c ykman fido credentials list

If the command above outputs a string mentioning "ssh" or "openssh", then you have already got a key generated and store on your YubiKey.

Evaluating additional authentication factors

Before generating a new ssh key to store on your YubiKey you must consider which additional required authentication factors you want to use. Below you can see a table with the available factors and their corresponding command:

ICS: Cinderella Tokens: An Async/IBC friendly alternative to flash loans

Flashloans are a fascinating economic coordination mechanism that has emerged out the Ethereum architecture as a result of a synchronous, sequential, atomic transaction system. It allows anonymous coordination between capital providers and arbitrageurs because the capital providers can condition providing any capital on protocol enforced guarantee that the entire arbitrage is profitable denominated in the token being lent.

One of the effects of this process has been the it ensures an efficient and healthy liquidation market for the collateral in long term debt instruments. It also enables low cost scaling of economic exploits.

Why don’t flash loans exist in IBC world?

Flash loans are impossible in an IBC world because IBC semantics require finalizing a block on the origin chain rather than on the receiving chain. This makes atomicity for the lender difficult and moves us into the domain of over collateralized lending.

I heard some points of criticism to how React deals with reactivity and it's focus on "purity". It's interesting because there are really two approaches evolving. There's a mutable + change tracking approach and there's an immutability + referential equality testing approach. It's difficult to mix and match them when you build new features on top. So that's why React has been pushing a bit harder on immutability lately to be able to build on top of it. Both have various tradeoffs but others are doing good research in other areas, so we've decided to focus on this direction and see where it leads us.

I did want to address a few points that I didn't see get enough consideration around the tradeoffs. So here's a small brain dump.

"Compiled output results in smaller apps" - E.g. Svelte apps start smaller but the compiler output is 3-4x larger per component than the equivalent VDOM approach. This is mostly due to the code that is usually shared in the VDOM "VM" needs to be inlined into each component. The tr

Resign Expo IPA for associatedDomains

You can also generalize these instructions to modify your ipa for any other reason.

Error message

ERROR ITMS-90046: "Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value '*' for key 'com.apple.developer.associated-domains' in 'Payload/Exponent.app/Exponent' is not supported."

Assumptions

My app id is io.getsparks.sparks
My distribution certificate name is iPhone Distribution: Boost Labs, Inc

Installing ngrok on OSX

For Homebrew v2.6.x and below:

brew cask install ngrok

For Homebrew v2.7.x and above:

	import React from 'react'
	import { withRouter, Link } from 'react-router-dom'
	import { graphql, compose } from 'react-apollo'
	import { Formik } from 'formik'
	import Yup from 'yup'

	import FormWideError from '../elements/form/FormWideError'
	import TextInput from '../elements/form/TextInput'
	import Button from '../elements/form/Button'
	import { H2 } from '../elements/text/Headings'

	function WhySoManyProps(props) {
	const user = extractUser(props);
	const fudge = calculateFudge();
	const bits = computeBits();

	// This is soooooo redundant.
	return <SomeComponent user={user} fudge={fudge} bits={bits} />;
	}

	function Shorthand(props) {

	// 1. Define a state variable for showing/hiding the action-button
	state = {
	isActionButtonVisible: true
	}

	// 2. Define a variable that will keep track of the current scroll position
	_listViewOffset = 0

	// 3. Add an onScroll listener to your listview/scrollview
	<ListView

	// connect() is a function that injects Redux-related props into your component.
	// You can inject data and callbacks that change that data by dispatching actions.
	function connect(mapStateToProps, mapDispatchToProps) {
	// It lets us inject component as the last step so people can use it as a decorator.
	// Generally you don't need to worry about it.
	return function (WrappedComponent) {
	// It returns a component
	return class extends React.Component {
	render() {
	return (

	var React = require('react-native')
	var {
	View,
	Text,
	LinkingIOS,
	StyleSheet,
	} = React

	// you might want to compile these two as standalone umd bundles
	// using `browserify --standalone` and `derequire`