Joyboy protocol draft specification

[AbdelStark]

Joyboy Protocol Specification Proposal

Introduction

The Joyboy protocol aims to leverage the decentralized nature of the Nostr protocol combined with the programmable capabilities of Starknet's account abstraction. Joyboy enables users to trigger onchain actions on Starknet through Nostr signed messages. This document provides a comprehensive specification for the Joyboy protocol, starting with two primary use cases: social pay and memecoin deployment and trading.

Protocol Overview

The Joyboy protocol defines a set of commands that users can send via Nostr messages to perform specific actions on Starknet. Each command follows a structured format and is signed using the user's Nostr private key. The protocol ensures that the commands are validated and executed securely on the Starknet blockchain.

Commands

Social Pay

The social pay command allows users to send tips in the form of tokens to other users. The command structure is as follows:

Command Structure:

joyboy send <AMOUNT> <TOKEN_SYMBOL> to <RECIPIENT_HANDLE>

Example:

joyboy send 10 STRK to @vbuterin

Explanation:

• joyboy send: The action identifier for sending tokens.
• <AMOUNT>: The amount of tokens to be sent.
• <TOKEN_SYMBOL>: The symbol of the token to be sent.
• to <RECIPIENT_HANDLE>: The recipient's handle on the Joyboy platform.

Memecoin Deployment and Trading

The memecoin command allows users to deploy new memecoins and trade them. The command structure is as follows:

Command Structure:

joyboy meme new <TOKEN_NAME> <TOKEN_SYMBOL> <TOKEN_SUPPLY>

Example:

joyboy meme new Dogecoin DOGE 100000

Explanation:

• joyboy meme new: The action identifier for deploying a new memecoin.
• <TOKEN_NAME>: The name of the new token.
• <TOKEN_SYMBOL>: The symbol of the new token.
• <TOKEN_SUPPLY>: The total supply of the new token.

Message Signing and Validation

Every command sent via the Joyboy protocol must be signed using the sender's Nostr private key. The signature ensures the authenticity and integrity of the message. Clients will validate these signatures before forwarding the commands to Starknet.

Message Format

TODO: Map this with NIP compliant format.

Each message must include the following components:

• Command: The specific Joyboy command to be executed.
• Timestamp: The time at which the command was created.
• Public Key: The sender's public key.
• Signature: The Nostr signature of the message.

Example:

{
  "command": "joyboy send 10 STRK to @vbuterin",
  "timestamp": "2024-05-17T10:00:00Z",
  "public_key": "npub1examplepublickey",
  "signature": "nosesignatureexample"
}

Onchain Action Execution

Upon receiving a valid command, the Joyboy client will interact with the custom Starknet account contract to execute the corresponding onchain action. The custom account contract will be programmed to recognize and execute the Joyboy protocol commands.

Security Considerations

• Authentication: Ensure all commands are signed and validated using Nostr signatures.
• Authorization: Only authorized users (validated via their public key) can perform actions on their accounts.
• Replay Protection: Implement nonce or timestamp mechanisms to prevent replay attacks.

TODOs

1. Design Questions:

   • How to handle command queuing and execution order?
   • What happens in case of command conflicts or failures?

2. Challenges:

   • Ensuring scalability and performance of the Joyboy protocol.
   • Handling edge cases and potential security vulnerabilities.

3. Further Development:

   • Implement additional use cases and commands.
   • Develop a comprehensive testing framework for the protocol.
   • Create detailed documentation and tutorials for developers and users.

Conclusion

The Joyboy protocol aims to bring decentralized social media interactions and onchain actions together, leveraging the strengths of Nostr and Starknet's account abstraction. This initial specification provides a foundation for further development and refinement, ensuring a secure and efficient protocol for the Joyboy platform.