Background Superrare: https://superrare.com/artwork/eth/0x82a870e295b8dcb8de2095529bff1b0697aa361b/let-me-check-with-the-wife--1 Etherscan: https://etherscan.io/address/0x82a870e295b8dcb8de2095529bff1b0697aa361b Secondary Token: https://opensea.io/collection/marital-obligations Etherscan https://etherscan.io/address/0x0169b5e4059b18d3bc5002c56b72d512bf67fe37 Basically we minted an artwork (let me check with the wife) on SuperRarethen created a 2nd contract called Marital Obligations (which is a dynamic SVG nft we can update with prompts to the collector). It uses the Owner(Of) function so that it is forever tied to LMCWTW SuperRare minted piece.

Here are a few tips to keep in mind when interacting with any dApps and smart contracts, including the Human Unreadable project. Project Addresses Human Unreadable Act II https://etherscan.io/token/0x15878dF6BF7a5dA17e12Ba80f1a635211f3Dbae4 Artblocks Contract Address (Act I) https://etherscan.io/address/0x99a9B7c1116f9ceEB1652de04d5969CcE509B069 Claiming Act II token

The primary collection of Human Unreadable is the Artblocks collection here: https://etherscan.io/address/0x99a9b7c1116f9ceeb1652de04d5969cce509b069 https://opensea.io/collection/human-unreadable-by-operator Token IDs range from 455000000 to 455000399 The secondary collection of Human Unreadable Act II is the contract here: https://etherscan.io/address/0x15878df6bf7a5da17e12ba80f1a635211f3dbae4

Phage is a rust based library that provides a set of middleware for Ethereum nodes. The middleware is designed to be modular, and extensible, enabling developers to program the Ethereum node to understand the intent of the user, and take the optimal action on their behalf. Using the middleware, developers can build applications that are more secure, more efficient, and more user friendly. In this article, we will explore the different types of modules that can be built using this middleware, including: Multi-Party Computation based transaction signing AI threat interception Opt-in compliance management Transaction fee optimization Sender based restrictions and alerting Transaction broadcasting strategy optimization

Q. Do you think more crypto companies would turn towards PYUSD over other non-regulated stablecoins and even market leaders like USDT and USDC? Dollar backed stablecoins play a key role in building global, accessible financial infrastructure. Stablecoins allow people around the world to access safe ways to save, borrow, and handle payments, especially if they live in an area with volatile and unpredictable FIAT options. They also offer investors a way to balance their exposure to riskier cryptoassets without having to move their assets off chain. However, dollar backed stablecoins introduce centralization and regulatory risks as they are issued and managed by companies that interface with the traditional banking system and are subject to inconsistent regulations depending on where they are based. It would be wise for crypto companies to support PYUSD in addition to other dollar backed stablecoins in order to distribute risk and minimize the impact of one institution failing, whether due to regulatory changes, hacks, or smart contract vulnerabilities. Earlier this year USDC was impacted by the collapse of banks holding the dollars backing their stablecoin, leading to a temporary drop of USDC value. USDT and PYUSD could both face similar challenges in the future. By supporting a suite of stablecoins and allocating risk appropriately crypto companies can get the benefit of dollar backed stablecoins without being fully reliant on one institution. However, even multiple separate institutions may be affected by the same systemic risks and crypto companies should seek uncorrelated assets to further mitigate their risks. In addition, if PYUSD’s regulatory position is superior to USDC an USDT for adoption in markets like the US, it may open opportunities for building new types of on chain saving, payments, and investment infrastructure for the US market, which has historically been excluded from accessing certain crypto applications due to US regulatory burdens. Q. Do you think PayPal's decision to enter the stablecoin market might prompt other payment processors like Visa and Mastercard towards more niche crypto payment solutions? I do expect other payment processors to start introducing their own stablecoins and other crypto native finance products. While the market may seem small and niche to them now, they should soon realize the efficiency, accessibility, and security gains that are enabled by building infrastructure on a global blockchain. Last month Gnosis announced Gnosis Pay which allows people to seamlessly move funds between bank accounts and cryptowallets through a debit card. They are working with a number of banks and traditional payments processors to roll this out and it’s a great demonstration of what can be done when traditional and web3 infrastructure works together. Q. What are your thoughts on some early code vulnerabilities and centralization concerns around the stablecoin with some suggesting Paypal can wipe out customer balance in just two commands? Dollar backed stablecoins are centralized by nature. Some institution has to hold the assets backing the tokens, and they are subject to banking and financial regulations both where they are based, and all the markets in which they intend to operate. Earlier this week the Federal Reserve in the US published a notice reminding banks that they have to manage their operational, cybersecurity, liquidity, sanction, and consumer protection risks when supporting stablecoins, the same way they have obligations for traditional banking products. The ability to freeze and seize funds are important functions for the stablecoin to have in order to meet regulatory expectations. PYUSD is not unique in having the ability to freeze and seize funds. USDC also has the ability to freeze funds.

https://docs.shield3.com/reference/policy-1 Shield3 has a general purpose policy engine which validates transactions using both static checks and real time data. All transactions that flow through our RPC are checked against a set of default, and customer defined policies. Transactions can either be allowed, blocked, or flagged for secondary confirmation. Policies are defined as JSON documents like this { "scope": {

Subgraph transaltion to DAOstar JSON LDAPI developed, deployed, documented Supports Gnosis, DAOstack, Moloch, Aave Specs updated & deployed to all major EVM networks Subgraphs deployed Subgraphs integrated into front end exploration Smart contact regisry updated on spec

The following updates need to be made on all supported EVM networks: Contracts Deploy to all networks https://github.com/metagov/daostar/blob/60fd73998dee7f840230c66f60834f962891a469/contracts/package.json#L9 Only goerli has been completed "scripts": { "build": "forge build",

Company: Shield3 (Shield3.com) Location: Remote Position type: Flexible (FT or Contract) About Us: Shield3 is an innovative web3 security and fraud prevention startup dedicated to providing cutting-edge, consumer-facing SaaS solutions. We are a small, agile team of 10 employees who are passionate about creating a safer and more secure digital landscape for consumers.

Chain selection Running Contractooor (for agreements) Token doesn't need mainnet liquidity Work with snapshot Work with Sablier Work with Gnosis Safe Decision: Deploy on Optimism

All DAOs experience culture drift, periods of dormancy, rejuvination, and other things to be expected in a dynamic group. After the initial period of excitement, core members inevitably move on to other interests and newcomers begin to define the culture. Rather than combat culture drift, all DAOs should simply have an expiration date at which time all funds are frozen or dissolved. Culture drift DAOs combat culture drift in various ways. Lore building in hopes of achieving a mythology that outlasts any single member Closing off new memberships after an initial setup period Hiring operators to keep members engaged Culture drift is natural, and combating it feels like trying to stay afloat in a riptide. What if we instead introduced a protocol that automatically freezes and dissolves all DAOs after a set period.

October 31 We arrived first to the Chateau, in a car with Colborn, Gordon, Bea, and P. We chose to approach from the cinematic direction, with the Chateau rising over the gate as we climbed the driveway. Fey has been refreshed with a Miami Vice aesthetic, full of soft pink couches and mirrored surfaces. I recorded some walkthroughs of the liminal spaces and imagined some of the ways they will change once the residents arrive and start adapting them to their projects. P gave us a tour of the grounds. The recent Fey Arts event activated many spaces I remember as storage for machinery and furniture. They have been transformed into welcoming spaces filled with tables, carpets, bars, and remnants of art installations. During the tour I discovered many spaces I didn’t encounter on my three previous stays here. The rare fruits and veggies garden, the native plant labyrinth with lifeguard chair for safety, the indoor sports arena, the courtyard tower, and the cottage where I will be sharing a room with three other residents. I was also reintroduced to the Kugel auditorium and was happy to find it still standing strong, just with sun bleached webbing. One resident was expected to arrive by priority air shipment. A Pepe the Frog doll exiled from America is permanently moving to France where public perception is more nuanced and less entangled with cultures of hate. The human residents slowly arrived throughout the afternoon and got settled into their rooms. While we reunited with old friends and collaborators the new chefs, Dan and Harry, grilled a large carcass and play punk rock on the kitchen stereo.

Notes based on call between Isaac and Sabeen on October 25 Context Consensys intends to foster growth and build relationships influential developers and leaders in the Eth ecosystem. We discussed a few potential experiments, both immediate and near term that we can collaborate on to accomplish this. Logos is a DAO Exchange that educates and onboards newcomers direclty into DAOs and connects them to the perfect group for them to grow. We have direct the best netowrk of both promising newcomers and established leaders and influencers in the DAO space In this doc we summarize some experiments we can run together. Cosponsoring a grants DAO with Logos

This document outlines the initial architecture of the Hydra DAO and is intended to coordinate the onboarding of funds, members, and tech deployment. Initial Architecture Treasury Hydra's treasury will exist on mainnet and be managed in a Gnosis Safe. Initially the Safe will be configured with multisig signers, but we can later upgrade to direct governance tooling. Share Accounting Shares will use a modified ERC20 contract which implements transfer restrictions. The following restrictions will be implemented: Allowlist of holders

TL;DR Many DAOs desire gasless voting solutions to make participation easier for members. Some gasless voting solutions that have been adopted by DAOs rely on easily exploited oracle systems to bring votes on chain for execution. A real world example is demonstrated where ~$20,000, or 50% of a DAOs treasury was taken through a fraudulent transaction. Other DAOs that have implemented the same system manage individual treasuries exceeding $10-20M. There are simple steps these DAOs can take to safeguard their treasuries, but the exploit highlights an issue in composable governance and treasury management where tools are adopted without thorough vetting and proper configuration. Intro Blockchains only know information that is internal to itself. This includes a wallet's balance of an asset for the native network currency, a wallet's balance of a governance token issued by a DAO, the owner of an NFT, and to some extent information about itself like the current time & date, block number, and other protocol metadata. But if you ask a blockchain about something external, like the weather, a stock price, the exchange rate of two fiat currencies, or the results of an off chain vote, it will have to rely on some trusted place to source that information. These data sources are called Oracles. Oracles can be implemented in various ways. The most popular oracle provider is Chainlink, which supplies market data, verifiable randomness, weather, and many other data feeds to smart contracts. Markets secured by Chainlink exceed $20B in assets. In the Chainlink ecosystem, node operators are paid in LINK tokens to provide accurate real-world data. Node operators must also stake LINK to provide data. Staked LINK can be taxed or slashed if dishonest behavior is detected. Reality.ETH is the oracle system that is the main focus of this analysis. At the time of this analysis, DAOs guarding their treasury with a Reality.eth module have a total value exceeding $30M.

Intro The topic of 'Login with Ethereum' came up during Vitalik's talk at EthCC.https://youtu.be/oLsb7clrXMQ?t=1450 I wanted to demonstrate how easy this is to implement in practice using a serverless backend and a simple web3 enabled frontend using simple signatures for authentication while checking against the public key (the ethereum adress) to verify if the signature is correct. This guide demonstrates how to integrate 'log in with Ethereum' with a serverless API on AWS. The front end is based on Scaffold-ETH. How it works