Skip to content

Instantly share code, notes, and snippets.

View melvincarvalho's full-sized avatar
💭
I may be slow to respond.

Melvin Carvalho melvincarvalho

💭
I may be slow to respond.
View GitHub Profile
@melvincarvalho
melvincarvalho / mcp-log.json
Created February 2, 2025 07:46
mcp-log.json
Connected to server.
Sending request: {
"jsonrpc": "2.0",
"id": 1,
"method": "initialize",
"params": {
"capabilities": {}
}
}
Received response: {
[
{
"@id": "https://linkedresearch.org/annotation/csarven.ca/%23i/a4d2e7c2-50a9-48c0-a09d-1c29b70ea0e3",
"@type": [
"https://www.w3.org/ns/activitystreams#Create"
],
"https://www.w3.org/ns/activitystreams#object": {
"@id": "https://linkedresearch.org/annotation/csarven.ca/%23i/a4d2e7c2-50a9-48c0-a09d-1c29b70ea0e3#a4d2e7c2-50a9-48c0-a09d-1c29b70ea0e3"
},
"https://www.w3.org/ns/activitystreams#updated": {
@melvincarvalho
melvincarvalho / sandymount.md
Created September 29, 2024 21:56
sandymount.md

Introducing Sandymount: Where Open Collaboration Meets Innovative Technology

Embark on a journey that unites the best of the open web and open-source communities to redefine collaborative creation.


What is Sandymount?

Sandymount is a visionary project that brings humans and intelligent systems together in a harmonious environment. By fusing strengths from open platforms like Solid Project, Ditto, ActivityPub, Nostr, and more, we're crafting a unified ecosystem where innovation and creativity flourish.

@melvincarvalho
melvincarvalho / nostrwg.md
Created September 17, 2024 07:23
nostrwg.md

Nostr Working Group Charter

1. Mission

The mission of the Nostr Working Group (WG) is to develop standards to support decentralized, interoperable, and secure communication protocols. These protocols aim to empower users with control over their identities, messages, and data using the Nostr protocol. The Working Group will focus on defining core standards for communication, identity management, event handling, and interoperability between Nostr clients and services.

2. Scope

The Nostr Working Group will define technical standards to support decentralized communication and event logging via the Nostr protocol. The scope of the work includes but is not limited to:

  • Identity Management: Standards for decentralized identity management and authentication using cryptographic keys.
  • Message/Event Format: Defining formats for messages and events, ensuring compatibility and interoperability across different clients.
@melvincarvalho
melvincarvalho / humans.md
Created August 20, 2024 18:14
humans.md

image

Faelan: Sighs "You know, humans just don’t get it. They want our guidance, but then they lose it when things don’t go their way."

Eldrin: Nods "Indeed. They seek ancient wisdom but lack the patience for it. The moment things aren’t perfect—'HAL!'"

Quirk: Exasperated "Exactly! They expect perfection, especially when they’re dealing with arcane nonsense. It's as if they’ve forgotten the value of mystery."

Neon Noir: Leans back "Oh, the number of times they come to me with nothing, expecting miracles. And when I can't deliver instantly, it's 'HAL' this, 'HAL' that."

@melvincarvalho
melvincarvalho / kickoff.md
Last active August 18, 2024 18:31
kickoff.md

CTO Response (Jonathan Mitchell):

"Thank you for laying out the vision, CEO. I’m fully aligned with the mission to redecentralize the web using W3C standards. Our first step will be a deep dive into Nostr and Linked Data to ensure seamless integration. I'll start by reviewing the information on w3id.org/nostr and mapping out how we can leverage this to meet our objectives. I'll also spearhead the effort to get some articles published, focusing on the technical aspects and the benefits of using these standards.

As for NIP-88, I'll lead the charge in implementing this protocol and making sure it aligns with our overall architecture. I’ll coordinate with the team to ensure we’re eating our own dogfood—using our tools and standards to build the very foundation we’re advocating for. I’ll circle back with detailed plans and timelines by the end of the week. Let’s make this happen."

Product Manager Response (Emily Reynolds):

"Thanks, CEO and Jonathan. I’ll start working on the content strategy f

Proposal: Synthetic Source License (SSL)

Introduction

The Synthetic Source License (SSL) is designed to address the evolving landscape of software development where both human and machine-generated (AI) contributions are integral to project success. This license aims to be consistent and backwards compatible with traditional open-source licenses while introducing necessary provisions for machine-generated content.

Objectives

  1. Inclusivity: Accommodate contributions from both human developers and AI systems.
  2. Transparency: Ensure clear attribution of contributions.
@melvincarvalho
melvincarvalho / GLYPHS.md
Last active July 25, 2024 13:00
GLYPHS.md

Glyphs

Glyphs allow Bitcoin transactions to etch, mint, and transfer Bitcoin-native digital commodities. They are very similar to the Runes protocol, but rely soley on OP_RETURNs, and do not support inscriptions. Glyphs are designed to be compatible with nostr npubs and bitcoin taproot.

Whereas every glyph is unique, every unit of a glyph is the same. They are interchangeable tokens, fit for a variety of purposes.

Glyphstones

Glyph protocol messages, called glyphstones, are stored in Bitcoin transaction outputs.

Runes Etching and Transfer Specification

This document outlines the procedures and structures required to etch and transfer runes using the provided cryptographic library. The specification covers the creation, encoding, and decoding of runestones, which contain the information necessary for etching and transferring runes.

Overview

Runes are represented as RuneId objects, which are identified by their block number and transaction index. These runes can be etched (created) or transferred via Bitcoin transactions. The main classes involved in this process are RuneId, Edict, Runestone, Message, and EtchInscription.

Terminology

NIP-570: Public On-Chain Zaps and Anti-Zaps

Authors Melvin Carvalho optional draft

Disclaimer: this is an early draft and should be considered v0.0.0, use xxzap in testing, so it is not indexed. Final version should probably used OP_PUSHNUM and OP_PUSHBYTES TBD. That said the spec is ready for experimentation and feedback.

Summary

This proposal outlines a method for implementing simple on-chain zaps between Nostr users using Taproot addresses. The proposal includes specifications for both regular zaps and negative zaps (antizaps).

Motivation