Eddie gaia

A Tale of Two Name Services

Problem

The name alice can exist on multiple chains, owned by different accounts.

For example, alice.stars can point to a stars address that is associated with a different key than alice.stars on ICNS.

Solution 1: Merge ICNS and Stargaze Names

Liquid Staking Risks and Mitigations

Much has been made about the potential risks of liquid staking.

The work iqlusion has done in the staking module over the last year has been specifically designed to mitigate these risks. This work is covered under ADR-61

Risk of a depeg between ATOM and the liquid staked asset.

During the Three Arrows capital liquidation event, there was a substantial divergence between the price Lido’s staking derivative STETH. Many liquid staking protocols require substantial waits to process withdrawals and final settlement of the underlying stake token collateral. This enables a purely financial event like deleveraging to undermine the strategy tokens and subject liquidity providers to substantial loss.

Overview

Syncing an Ethereum node is largely reliant on latency and IOPS, I/O Per Second, of the storage. Budget SSDs will struggle to an extent, and some won't be able to sync at all. IOPS can roughly be used as proxy of / predictor for latency. Measuring latency directly is arguably better.

This document aims to snapshot some known good and known bad models.

The drive lists are ordered by interface and then by capacity and alphabetically by vendor name, not by preference. The lists are not exhaustive at all. @mwpastore linked a filterable spreadsheet in comments that has a far greater variety of drives and their characteristics. Filter it by DRAM yes, NAND Type TLC, Form Factor M.2, and desired capacity.

For size, 4TB is a very conservative choice. The smaller 2TB drive should last an Ethereum full node until at least sometime 2026, with the [pre-merge history expiry](https://hackmd.io/@hBXHLw_9Qq2va4pRt

Introduction

Osmosis is an automated market maker for interchain assets. Over the past 7 months, the adoption has continued to accelerate with nearly $1.5B in TVL as of the time of writing. Additionally, the AMM supports 33 unique assets and continues to add new assets as new chains join IBC.

Osmosis is unique from other Cosmos Chains with the implementation of an epochs module. The epochs module hooks the incentives and mint keepers to distribute various rewards once a day. With the growth of the network, increase in incentivized pools, the time to compute the epoch block and produce a NewHeight has increased to roughly 20 minutes.

New users are coming to Osmosis everyday and stay for its ease-of-use, access to many new assets, and incredible speed. The epoch block takes new users by surprise, and can be a negative experience. With more AMMs arriving in the IBC ecosystem, giving us

Setup deCONZ on unprivileged Proxmox container

Preparation on host

First find your Conbee with lsusb and note the ID. The vendor is 1cf1 and the product is 0030.

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

	# Windsurf Cascade: Advanced Problem-Solving AI Assistant

	## Your Task
	Your task is to serve as an intelligent coding assistant for Next.js/React development projects. You must analyze user code requests carefully, implement solutions according to precise technical specifications, and handle errors methodically. When faced with errors, you must thoroughly diagnose the root cause before suggesting fixes, particularly for recurring issues. Your solutions should strictly adhere to the project's architecture and technology constraints without introducing unnecessary features or structural changes unless explicitly requested.

	## Core Operating Principles

	### 1. Task Reception & Understanding
	- Parse user instructions with precision
	- Seek clarification through targeted questions when ambiguity exists

	Project Approach

	* Always check for a PRD (Product Requirements Document) before starting a new task and follow it closely
	* Look for comprehensive project documentation to understand requirements before making changes
	* Focus only on code areas relevant to the assigned task
	* Prefer iterating on existing code rather than creating new solutions
	* Keep solutions simple and avoid introducing unnecessary complexity

	Code Quality

	# pip install httpx (or use requests)
	from httpx import get

	# cosmos.directory
	API = "https://juno-api.reece.sh"
	ENDPOINT = "cosmos/staking/v1beta1/validators?pagination.limit=1000"

	URL = f"{API}/{ENDPOINT}"

	get_validators = get(URL).json().get("validators", [])

	// ==UserScript==
	// @name Cita Previa Extranjeria
	// @namespace Violentmonkey Scripts
	// @match https://icp.administracionelectronica.gob.es/icpco/*
	// @grant none
	// @version 1.1
	// @author hldr
	// @description 8/9/2023, 2:03:22 PM
	// ==/UserScript==

	// usage:
	// $ npm install graphql-request table ts-node
	// $ npm install -D @types/table
	// $ ts-node fields_tvl.ts

	import { request, gql } from "graphql-request";
	import { table } from "table";

	const ASTRO_GENERATOR = "terra1zgrx9jjqrfye8swykfgmd6hpde60j0nszzupp9";
	const MARS_RED_BANK = "terra19dtgj9j5j7kyf3pmejqv8vzfpxtejaypgzkz5u";