o-az

Kitty Remote Control Protocol Documentation

Overview

Kitty's remote control system allows external programs to control kitty terminal instances through a JSON-based protocol. This enables programmatic control over windows, tabs, colors, text, and more.

Source References:

• Remote Control Tutorial
• Protocol Specification
• Launch Command

o-az

#!/usr/bin/env bash

# SwiftBar plugin: Open Listening Ports Monitor
# Displays open TCP listening ports and lets you kill your own processes

current_user=$(whoami)

# Get listening ports with numeric values only
open_ports=$(lsof -iTCP -sTCP:LISTEN -n -P 2>/dev/null | awk -v cu="$current_user" 'NR > 1 {
    user = $3

o-az

Proposing accepting TypeScript-based config file/s for oxfmt and oxlint.

Proposed options:

• Separate config files: oxlint.config.ts, oxfmt.config.ts
• Single config file for both: oxc.config.ts

Separate

oxfmt.config.ts variation 1:

o-az

#!/usr/bin/env node --experimental-strip-types --no-warnings
var Ix=Object.create;var{getPrototypeOf:Lx,defineProperty:Z0,getOwnPropertyNames:Kx}=Object;var Ux=Object.prototype.hasOwnProperty;var h=(b,B,A)=>{A=b!=null?Ix(Lx(b)):{};let C=B||!b||!b.__esModule?Z0(A,"default",{value:b,enumerable:!0}):A;for(let g of Kx(b))if(!Ux.call(C,g))Z0(C,g,{get:()=>b[g],enumerable:!0});return C};var _0=(b,B)=>()=>(B||b((B={exports:{}}).exports,B),B.exports);var M=_0((g1,o)=>{var k=process||{},q0=k.argv||[],j=k.env||{},Yx=!(!!j.NO_COLOR||q0.includes("--no-color"))&&(!!j.FORCE_COLOR||q0.includes("--color")||k.platform==="win32"||(k.stdout||{}).isTTY&&j.TERM!=="dumb"||!!j.CI),Hx=(b,B,A=b)=>(C)=>{let g=""+C,f=g.indexOf(B,b.length);return~f?b+Wx(g,B,A,f)+B:b+g+B},Wx=(b,B,A,C)=>{let g="",f=0;do g+=b.substring(f,C)+A,f=C+B.length,C=b.indexOf(B,f);while(~C);return g+b.substring(f)},w0=(b=Yx)=>{let B=b?Hx:()=>String;return{isColorSupported:b,reset:B("\x1B[0m","\x1B[0m"),bold:B("\x1B[1m","\x1B[22m","\x1B[22m\x1B[1m"),dim:B("\x1B[2m","

o-az

└── apps
    └── contract-verification
        ├── reset.d.ts
        ├── .env.example
        ├── container
            ├── tsconfig.json
            ├── compiler.ts
            └── index.ts
        ├── scripts
            ├── local-d1.sh

o-az

#!/usr/bin/env bash

set -euo pipefail

TEMPO_RPC_URL="https://rpc-orchestra.testnet.tempo.xyz"
# NOTE: This is a throaway PK created for this test
PRIVATE_KEY=${PK:-"0xa4b3490c35582d544451fbbfd7a0e4c5fa4d0ded06563ccc199057c7a5e6c9de"}
VERIFIER_URL=${VERIFIER_URL:-"https://contracts.tempo.xyz"}

TEMP_DIR=$(mktemp -d)

o-az

flowchart LR
    %% Data Sources
    Node["EVM Node (Local or RPC)"]

    %% AMP Core
    subgraph AMP["AMP Indexer"]
        Extract["Block and Log Extraction (Parallel)"]
        Raw["Raw EVM Datasets Parquet in Object Storage"]
 Compact["Compaction Optimized Parquet"]

o-az

<h1 id="evm-benchmark-results">EVM Benchmark Results</h1>
<p><em>Times shown are per-execution averages from 1 internal runs per benchmark.</em></p>
<table>
<thead>
<tr>
<th>Benchmark</th>
<th>Guillotine (ms)</th>
<th>REVM (ms)</th>
<th>ethrex (ms)</th>
<th>Guillotine-Rust (ms)</th>

o-az

Self-Hosting Sourcify for Custom Chains

I initially followed the guide here: https://docs.sourcify.dev/docs/running-server.

I encountered some issues so I'm writing this guide based off-of the original one.

Prerequisites

• PostgreSQL 16+
• Node.js LTS

o-az

can u open http:​//localhost:4434 n a browser and take a screenshot? dev server already up

---

Claude Code