Mike Purvis mikedotexe

This document is a personal document and does not represent the views of the company. This document is in draft form and I reserve to modify the contents of it.

The Scrypt of C฿J

! The days after Christmas, for personal reasons, it became clear to me that I had been living most of my life within the confines of guilt masked as love. This is just the circumstance of my personal life, something that chose me by chance or by fate, but somehow I was always aware of.
! When all the circumstances of my life and work came together under this new perspective, everything began to make sense. That I was too selfless to a fault (though some would say naive). And finally I could see why.
! I don’t wish to speak more about it for respect of those involved, and to keep their honor; and besides, I accept the imperfections that I have, if I don’t celebrate them.
! Until I settled in the Mission in San Francisco, I was always moving around, country to country, state to state. The only constant I knew w

Motivation

In 2023, we're seeing new and promising general-purpose, permissionless smart contract platforms launching in the interchain. This document is meant to cover thoughts on community management, avoiding trolls and toxicity, maximizing cooperation, and underscoring the landscape to expect as a sovereign-but-permissionless chain.

Forest for the trees

To set the stage, let's briefly zoom out and talk about the advent of public, community computers that have arrived in our lifetime.

In my lifetime, I saw the birth of the internet, and the confusion that hit the masses in the early day. We didn't know what to do with this thing. It could be argued that we didn't see the concrete possibilities, not because it wasn't properly explain, but because the idea was so incredibly broad and far-reaching, that it evaded us for decades. While we were building Geocities pages for fun, we didn't anticipate that online maps would be a regular part of daily navigation. Or that online deliveries would supplant i

To-Do List locally

We're going to get a local wasmd blockchain going, so we'll install that according to these instructions (after cloning the repo): https://github.com/CosmWasm/wasmd#quick-start

It's not a bad idea to create a new account in Keplr for testnet. We can use that seed phrase to store the same private key on your file system, securly via the operating system. What I mean by that is Mac users will see this when trying to use an app that wants to access it.

After you create an account on Keplr, you can find the mnemonic here:

The main things we need from token standards are minting and burning of fungible and non-fungible tokens, as well as events. We need to now determine if we SHOULD have standard function names for minting and burning, and if so, if they should be in a single standard or two. (For minting, for burning.)

Illia is proposing we do not have function names and instead only events:

(link to comment)

Wondering how this will work with NFT contracts "out there" that are using nft_mint that indexer and Wallet have worked around in order to show them as collectibles.

Opening

Is there a reason for no_std or is this synonymous with the goal of reduce contract size.
What's the criteria we're aiming for, which types of contracts are being built that the SDK is not optimized for.

What does an existing contract look like

Is it like Eugene's approach? (near/core-contracts#88 also more readable here: https://github.com/near/core-contracts/blob/882ded0634ee50ef134a82c1bbf53262ab8b1550/fast-fun-token/src/lib.rs)

Peek into the link above:

	// run with "node get-mpc-signature-from-tx-hash.js" or whatever name

	const { connect, keyStores } = require('near-api-js')

	const mockKeyStore = new keyStores.InMemoryKeyStore()
	const nearConfig = {
	keyStore: mockKeyStore,
	networkId: 'testnet',
	nodeUrl: 'https://archival-rpc.testnet.near.org',
	}

	const ProgressBar = VM.require("mike.near/widget/ProgressBar");
	console.log('props', props);
	const yoctoZeroes = "000000000000000000000000";

	const [stakingAmount, setStakingAmount] = useState("6");
	const [unstakingWithdrawlAmount, setUnstakingWithdrawlAmount] = useState("19");
	const StakeUnstakeWithdraw = ({ validator, method, amount }) => {
	const openAnotherModal = ({validator, method, amount}) => {
	// Let's explicitly have these in a switch so no one tries any funny business with methods
	switch (method) {

	#!/bin/sh

	SIMPLE_PAYROLL='{
	"create_task": {
	"task": {
	"actions": [
	{
	"msg": {
	"bank": {
	"send": {

	function set_cosmos_cli_config {
	# If you're using a pretty old shell, might remove "local"
	local cmd="$1"
	local chain_id="$2"
	local node="$3"
	local gas_prices="$4"
	local echo_str="$5"

	"$cmd" config chain-id "$chain_id"
	"$cmd" config node "$node"

	<html>
	<head>
	<title>Hello ChickTech 2019</title>
	<style>
	#top {
	background-color: lightblue;
	}
	body p {
	color: gray;
	}