pavanjoshi914

import { MetadataValidator } from './metadataValidator';
import AudioObject from '~/app/components/Metadata/AudioObject';

export function MetadataRenderer(metadata: string | undefined) {
  if (metadata != undefined) {
    const metadataObject: object = JSON.parse(metadata);
    const isMetadataValid: boolean = MetadataValidator(metadataObject);
    if (isMetadataValid) {
      for (const [key, value] of Object.entries(metadataObject)) {
        if (key == "type") {

pavanjoshi914

import { z } from "zod";
export const audioObjectSchema = z.object({
type: z.string(),
name: z.string().optional(),
creator: z.string().optional(),
image: z.string().optional(),
});

pavanjoshi914

import { audioObjectSchema } from "./audioObjectSchema";

export function isBase64(str: string) {
  if (str === "" || str.trim() === "") {
    return false;
  }
  try {
    return btoa(atob(str)) == str;
  } catch (err) {
    return false;

pavanjoshi914

🖼 ImageObject

Type ImageObject is a derived type from https://schema.org/ImageObject, which means that for this particular data model type, any of the properties also mentioned at schema.org, may also be used. However, to structure metadata supported properties mentioned shall be used only.

Properties

Required properties

| Property | Expected Type | Description |

pavanjoshi914

🎙 AudioObject

Type AudioObject is a derived type from https://schema.org/ImageObject, which means that for this particular data model type, any of the properties also mentioned at schema.org, may also be used. However, to structure metadata supported properties mentioned shall be used only.

Properties

Required properties

| Property | Expected Schema Type | Description |

pavanjoshi914

Context	Prefix	URL	Bundles	Prefix Required	Status
schema.org	schema	https://schema.org/	No	No	Living Standard
SKOS	skos	http://www.w3.org/2004/02/skos/core#	NO	No	Stable

pavanjoshi914

// custom type decleration of some of the arguments
type RequestInvoiceArgs = {
  amount?: string | number;
  defaultAmount?: string | number;
  minimumAmount?: string | number;
  maximumAmount?: string | number;
  defaultMemo?: string;
};

// webln provider class provides webln functionality and its exported so that in any file we can create an instance of the class and use the functionality class is providing.

pavanjoshi914

~By Pavan Joshi - Summer of Bitcoin 2022

A New Future of Bitcoin Transactions Resulting into Numerous Usecases💰

Abstract ⚡

pavanjoshi914

Abstract

Specifications such as Webln bought better solutions to the UX for lightning networks. On top of this, many broad applications such as instant payments via a web browser using Bitcoin Sats (eg. Alby), tippings for content writers, podcasts and streamers (Medium tipping via Alby) and many more came into working. Along with every transaction we can also store additional information in form of metadata which can make specification such as Webln more broad and applicative in terms of interactivity.

Transaction lists as we know them from our private bank accounts are often a simple list of transactions sorted by date. Each transaction has data like Sender, Receiver, amount, reason and date.

The aim of this proposal is to extend existing standards such as Webln to enrich transactions with additional information as structured metadata so that transactions containing static data contain more meaningful information giving more interactivity to the transactions.

webln.sendPayment method

pavanjoshi914

Mechanism::

client side

Extend sendPayment method with optional parameter metadata

sendPayment(paymentRequest: string, metadata?: string): Promise<SendPaymentResponse>;