-
- Crunchbase for info about companies, even private. Funding, acquisitions, people, etc. https://www.crunchbase.com/.
- Blind for anonymous internal chat about companies: https://www.teamblind.com/.
- Streaming protocols.
- Definitions.
- Stream = pay on periodic schedule.
- Vest = pay on periodic schedule, but with an end date, and allowing batches on certain dates (cliffs).
- Escrow = transfer to third-party smart contract instead of directly to recipient. It will hold until certain conditions are met, then finish the transfer. This allows cancellation during the holding period, obviously (“I put in the wrong address”).
- Venko for token streaming on Solana: https://github.com/VenkoApp/venko. Issue over a schedule, revocably or irrevocably. Escrow as well; hold over cancellation period.
- Streamflow is another on solana: https://github.com/streamflow-finance. Vest, pay, all the expectations. Connect your wallet to the dapp, specify a schedule/recipient, go.
- https://streamflow.finance/ and https://docs.streamflow.finance/.
- Their fees for vesting are 0.25%. https://docs.streamflow.finance/help/fees.
- Played around with it. Very simply to use: https://app.streamflow.finance/.
- Superfluid is another, but on ethereum: https://app.superfluid.finance/dashboard.
- Only streaming; doesn’t support vesting yet. Also looks like it’s just on L2s, not mainnet. Also you need to wrap your tokens before creating a stream.
- Fireblocks. A wallet on steroids, full-featured for corporate use. Basically a treasury, finance department, payroll, etc. A full platform to run a digital asset business. Can connect to exchanges, multiple wallets, lenders, etc.
- Justworks: https://justworks.com/. Really helpful platform for startups. Manages benefits, HR, compliance, payroll. They provide both software and consultants to help.
- ENS = Ethereum Name Service/System. DNS but for eth wallets, eth dapp websites, etc. https://ens.domains/. Identity provider; so we don’t have to deal with addresses.
- Fractal is an ID system as well: https://protocol.fractal.id/.
- Remember all eth addresses are hex numbers. 0x prefix just denotes hex.
- Party rounds = when multiple investors participate in an early funding round.
- Mirrortable = just a captable but mirrored onchain. https://balajis.com/mirrortable/. Smart contracts manage equity/tokens onchain, sure, but need to be synced with an offchain captable for all the standard auditing/compliance procedures.
- Solana Server Program: discounted access to cloud data centers where you can lease validators month-to-month. They do this to encourage decentralization.
- https://solana.foundation/server-program.
- There’s a similar Delegation Program, where you can essentially lease stake. You borrow sol (well, get sol delegated) from the Solana Foundation.
- Coinbase Cloud. APIs/infra for payments, data access, staking, more. https://docs.cloud.coinbase.com/.
- Bison Trails had a Query & Transact service (nodes as a service, allowing you to read and write onchain). This is now part of coinbase cloud. They also had a validator service that moved as well.
- Played with figma a little more. Collaborative design, history, wireframes, comments, all in browser. Can see it all live, UX and devs, clients and users, across the globe, changing in realtime.
- Can generate code from design. I’ve never seen a successful tool for this, usually the produced pseudocode is unusable; but I personally haven’t tried this feature on figma.
- IDO = initial DEX offering. It means you’re launching a token for the first time, and you’re doing it on a DEX.
- SolRazr. They call it a “developer ecosystem” – basically a solana incubator.
- They facilitate IDOs, offer developer tools and KYC integrations, help with fundraising, stuff that startups and new dapps might benefit from.
- I cannot tell you the last web3 project I’ve seen that DIDN’T use GitBook for docs. https://www.gitbook.com/.
- Alchemy provides HTTP APIs to fetch onchain info (for eth). Transactions, NFTs, token information, more.
- https://docs.alchemy.com/alchemy/enhanced-apis/transfers-api.
- AWS console. Played with a few different things on my account today.
- Amplify. Similar to GitHub/GitLab Pages. Connected it to GitLab, autoimported build/deploy configuration, hosted static site. Easy experience.
- Deployed https://bmahlstedt.gitlab.io/tic-tac-toe/ to https://main.d3jlirayiw5un4.amplifyapp.com/.
- In the free tier, you get (1000 build minutes / 5GB stored / 15GB served) per month.
- Launched an EC2 instance and played around.
- Amazon Linux AMI. t2.micro. 1 vCPU, 1GB mem, 8GiB SSD storage (EBS).
- Set up billing alerts.
- Remember “bips” phonetically = bps = basis points = hundredth of a percent.
- Coming back to tokemak: holding TOKE is like holding liquidity itself, in an abstract sense.
- Read a few more of their medium articles.
- Still think it’s weird how try to alias everything with cute names. Reactors, tokemechs, pilots…
- Did a little bit more churning research.
- Looked a little through the full web3.js lib: https://web3js.readthedocs.io/en/v1.7.0/.
- Refresher on redux. Rather than hoisting react state to the highest common component then flowing down (as props as necessary), you can store global state in redux; available to all components. Also isolates state modifiers as reducers, making them easier to test/understand/replay.
- Added redux devtools to brave.
- Remember (imperative = how) and (declarative = what). Give it steps to go from the current state to the final state, or give it the final state and let it resolve how to get there from the current state.
- Played with next.js and vercel.