title stringlengths 22 74 | content stringlengths 0 10.1k | url stringlengths 37 188 | code_snippets sequencelengths 1 8 ⌀ |
|---|---|---|---|
Introduction | Actions & Alerts | Introduction
Actions
Actions and Blinks are an ambitious new protocol in collaboration with Solana—& a developer stack by Dialect—to share Solana transactions everywhere.
Actions are a protocol for creating & delivering Solana transactions through URLs, making Solana sharable everywhere. Blinks, or Blockchain Links, ... | https://docs.dialect.to/documentation | null |
Actions | Actions & Alerts | Actions
Actions are APIs that deliver signable transactions, and soon signable messages.
Blockchain links, or Blinks, are clients that determine if URLs conform to the Actions spec, & introspect the underlying Actions APIs to construct interfaces for them.
Any client that fully introspects an Actions API to build a ... | https://docs.dialect.to/documentation/actions | null |
Quick Start | Actions & Alerts | These docs cover the Actions and Blinks specifications and how they work. For a more practical guide on creating your first action, testing and deploying it, and getting it ready to use on Twitter, see the Guide below.
If you're interested in building a Blinks client, see the Guide on building Blinks.
Last updated 24 ... | https://docs.dialect.to/documentation/actions/quick-start | null |
Specification | Actions & Alerts | Specification
This section of the docs describes the Actions Specification, including aspects of the specification that concern Blinks. Namely, it covers
URL Schemes
GET & POST schemas and capabilities
OPTIONS request and CORS handling
Execution and lifecycle
Multi-actions and action input types
The role of acti... | https://docs.dialect.to/documentation/actions/specification | null |
URL Scheme | Actions & Alerts | URL Scheme
Solana Actions conform to a URL scheme denoted by solana-action:. They are a set of standard, interactive HTTP requests for constructing transactions or messages for the client to sign with a wallet keypair.
Copy
solana-action:<link>
The link field must be a conditionally URL-encoded absolute HTTPS URL.
... | https://docs.dialect.to/documentation/actions/specification/url-scheme | [
"solana-action:<link>"
] |
POST | Actions & Alerts | POST
POST Request
Actions support HTTP POST JSON requests to their URL with the the body payload:
Copy
{
"account": "<account>"
}
where account is a base58-encoded representation of the public key of the user making the request.
Clients should use Accept-Encoding headers and the Action service should respond wi... | https://docs.dialect.to/documentation/actions/specification/post | [
"{account: <account>}",
"export interface ActionPostResponse {/** base64-encoded transaction */transaction: string;/** optional message, can be used to e.g. describe the nature of the transaction */message?: string;}",
"export interface ActionPostResponse<T extends ActionType = ActionType> {transaction: string;... |
OPTIONS & CORS | Actions & Alerts | OPTIONS & CORS
To enable Cross-Origin Resource Sharing (CORS) for Actions clients (including blinks), all Action endpoints must handle HTTP OPTIONS requests with appropriate headers. This ensures clients can successfully pass CORS checks for all subsequent requests from the same origin domain.
An Actions client may p... | https://docs.dialect.to/documentation/actions/specification/options-and-cors | null |
GET | Actions & Alerts | GET
Request
Action clients first make an HTTP GET JSON request to the Action URL. The request should be made with an Accept-Encoding header.
Response
The Action URL should respond with an HTTP OK JSON response with the body payload below, or with an HTTP error.
The client must handle HTTP client errors, server erro... | https://docs.dialect.to/documentation/actions/specification/get | [
"{title: Buy WIF with SOLicon: <url-to-image>description: Buy WIF using SOL. Choose a USD amount of SOL from the options below.label: Buy WIF}",
"{title: Buy WIF with SOLicon: <url-to-image>,description: Buy WIF using SOL. Choose a USD amount of SOL from the options below.,label: Buy WIF,links: {actions: [{label:... |
Execution & Lifecycle | Actions & Alerts | Execution & Lifecycle
We've describe the URL scheme, as well as the GET and POST APIs. Let's now describe the full Action execution flow, which follows a typical HTTP REST API lifecycle:
The client makes a GET request to the Action URL.
The Action API returns a GET response body of human-readable metadata describing... | https://docs.dialect.to/documentation/actions/specification/execution-and-lifecycle | null |
Multi-Actions | Actions & Alerts | Multi-Actions
To support multiple actions, Action Provider GET responses may include additional action URLs via the links attribute.
Copy
export interface LinkedAction {
/** URL endpoint for an action */
href: string;
/** button text rendered to the user */
label: string;
/** Parameter to accept user i... | https://docs.dialect.to/documentation/actions/specification/multi-actions | [
"export interface LinkedAction {href: string;label: string;parameters?: [ActionParameter];}export interface ActionParameter {name: string;label?: string;required?: boolean;}"
] |
actions.json | Actions & Alerts | https://docs.dialect.to/documentation/actions/specification/actions.json | null | |
Action Types | Actions & Alerts | Action Types
Linked Actions support both fixed as well as parameterized values, as specified by the optional parameters attribute.
Parameterized actions signal to the client that users may provide a variable input for the action.
Apart from simple text input fields, ActionParameter now also accepts other input types... | https://docs.dialect.to/documentation/actions/specification/action-types | null |
Actions | Actions & Alerts | Actions
Visit Dialect's Dashboard for a step-by-step guide to:
Create your first Action using open source, forkable examples in our Github.
Test your action on https://dial.to.
Register your action.
Share your Actions on Twitter, and bring them to life with Blinks support through your favorite extension like Phant... | https://docs.dialect.to/documentation/actions/actions | null |
Blinks | Actions & Alerts | Blinks
The Actions Spec v1 does not concern itself with visualization or layout, such as image, title, button or input positioning.
This is the responsibility of Blinks. In this section, we describe how blinks are constructed from actions, aspects of Blinks that are affected by the Actions specification, and other ma... | https://docs.dialect.to/documentation/actions/specification/blinks | null |
Building Actions with NextJS | Actions & Alerts | Building Actions with NextJS
In this section, you'll learn how to build a Solana Action. For the sake of this documentation, we'll be using NextJS to build it.
For code examples of Actions, check out our code examples or Solana Developers' code examples.
Codebase setup
Create a Next app through the CLI command and ... | https://docs.dialect.to/documentation/actions/actions/building-actions-with-nextjs | [
"npx create-next-app <your-action-codebase-name>cd <your-action-codebase-name>",
"npm i @solana/actions yarn add @solana/actions",
"import {ActionPostResponse,ACTIONS_CORS_HEADERS,createPostResponse,ActionGetResponse,ActionPostRequest,} from @solana/actions;",
"export const GET = async (req: Request) => {cons... |
Blinks | Actions & Alerts | Blinks
In the following sections, you can find how to add native blink support to your dApps through our React SDK, React Native SDK or even adding blink support to 3rd party sites through a Chrome extension.
If you've built an Action API and want to test the unfurling on an interstitial site, visit our Blinks specif... | https://docs.dialect.to/documentation/actions/blinks | null |
Add blinks to 3rd party sites via your Chrome extension | Actions & Alerts | Add blinks to 3rd party sites via your Chrome extension
This section is for Chrome extension developers who want to add Blinks to third party sites like Twitter. If you're interested in Native blink support check out our React SDK or React Native SDK.
Copy
// contentScript.ts
import { setupTwitterObserver } from "@d... | https://docs.dialect.to/documentation/actions/blinks/add-blinks-to-3rd-party-sites-via-your-chrome-extension | [
"import { setupTwitterObserver } from @dialectlabs/blinks/ext/twitter;import { ActionConfig, ActionContext } from @dialectlabs/blinks;setupTwitterObserver(new ActionConfig(RPC_URL, {signTransaction: async (tx: string, context: ActionContext) => { ... },connect: async (context: ActionContext) => { ... }}))import { t... |
Add blinks to your mobile app | Actions & Alerts | Add blinks to your mobile app
This section covers adding blinks directly to your React Native dApp through our React Native SDK for blinks. The SDK is completely open-source and can be found in our Github.
Installation
Copy
# npm
npm i @dialectlabs/blinks @dialectlabs/blinks-react-native
#yarn
yard add @dialectl... | https://docs.dialect.to/documentation/actions/blinks/add-blinks-to-your-mobile-app | [
"npm i @dialectlabs/blinks @dialectlabs/blinks-react-nativeyard add @dialectlabs/blinks @dialectlabs/blinks-react-native",
"import { useAction, type ActionAdapter } from @dialectlabs/blinks;import { Blink } from @dialectlabs/blinks-react-native;import { PublicKey } from @solana/web3.js;import type React from reac... |
Security | Actions & Alerts | Security
Actions and Blinks are a new way to interact with crypto transactions. They present both exciting new opportunities as well as new attack vectors for bad actors. Safety is high priority for this new technology.
As a public good for the Solana ecosystem, Dialect maintains a public registry — together with the... | https://docs.dialect.to/documentation/actions/security | null |
The Blinks Public Registry | Actions & Alerts | The Blinks Public Registry
We have made our Blinks Public Registry easily accessible through an API endpoint, and in a beautiful new interface on https://dial.to. Running a GET request on the endpoint will return JSON data of all the action APIs that have been submitted, registered and blocked from the registry
The B... | https://docs.dialect.to/documentation/actions/the-blinks-public-registry | null |
Alerts | Actions & Alerts | Alerts
Dialect Alerts is a smart messaging protocol for dapp notifications and wallet-to-wallet chat. We are powering notifications and messaging for over 30 of the most-loved dapps and wallets on Solana, EVM and Aptos.
All of our tooling is open source and free to use. Our on-chain messaging protocol, v0, is live &... | https://docs.dialect.to/documentation/alerts | null |
Alerts Quick Start | Actions & Alerts | Alerts Quick Start
An end-to-end guide on setting up notifications for your dapp.
This section provides an end-to-end quick start guide to get set up sending notifications to your users from your dapp. We get you set up for production use by walking through the following steps:
Create and configure your dapp keypair... | https://docs.dialect.to/documentation/alerts/alerts-quick-start | null |
Add blinks to your web app | Actions & Alerts | Add blinks to your web app
This section covers adding Blinks directly to your React dapp using our Blinks React SDK. The SDK is open-source and can be found in our Github.
Installation
Copy
# npm
npm i @dialectlabs/blinks
#yarn
yard add @dialectlabs/blinks
Adding the Blink Component
The following hooks are expo... | https://docs.dialect.to/documentation/actions/blinks/add-blinks-to-your-web-app | [
"import '@dialectlabs/blinks/index.css';import { useState, useEffect } from 'react';import { Action, Blink, ActionsRegistry } from @dialectlabs/blinks;import { useAction } from '@dialectlabs/blinks/react';const App = () => {const [action, setAction] = useState<Action | null>(null);const actionApiUrl = '...';const {... |
Getting started | Actions & Alerts | Getting started
To learn how to setup notifications, see the Notifications Quick Start Guide.
For a more in-depth guide to notifications for your dapp see the Notifications section. Or for a run through on how to send and receive messages with Dialect, which powers notifications under the hood, see the Messaging sect... | https://docs.dialect.to/documentation/alerts/getting-started | null |
Alerts & Monitoring | Actions & Alerts | Alerts & Monitoring
This section describes how to set up notifications for your dapp. The end-user experience is the ability for your user's to subscribe to receive timely notifications from your dapp over the channels they care about — SMS, telegram, email, and Dialect inboxes. Flexible tooling allows dapp developers... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring | null |
Decide How to Monitor Events | Actions & Alerts | Decide How to Monitor Events
Notifications can be triggered from a wide range of user behaviors and/or programmatic events. For example: NFT buyout requests, liquidation warnings, filled orders, new DAO proposals, new raffle listings, new social posts, etc.
Option 1: Use Dialect's Open Source Monitoring Tooling
Dial... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/decide-how-to-monitor-events | null |
Registering Your Dapp | Actions & Alerts | Registering Your Dapp
To get started, you must first register your dapp within the Dialect Cloud. Analogous to how businesses/users may register for web2 services via an email address, Dialect Cloud uses wallet authentication to register and manage dapps that use Dialect services.
Create a keypair for your dapp
Crea... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/registering-your-dapp | [
"const dapp = await sdk.dapps.create({name: 'My test dapp',description: `My test dapp's description.`,blockchainType: BlockchainType.SOLANA});"
] |
Using Dialect Monitor to Detect Events | Actions & Alerts | Using Dialect Monitor to Detect Events
Option 1: Use Dialect's Open Source Monitoring Tooling
Dialect has sophisticated, open-source tools for detecting events about changes to data (on- or off-chain) and turning those events into notification messages.
The first piece of this tooling is the Monitor library, an open-... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/decide-how-to-monitor-events/using-dialect-monitor-to-detect-events | null |
Learning to Use Monitor Builder: Supplying Data | Actions & Alerts | Learning to Use Monitor Builder: Supplying Data
A poll type data source is shown below. Within this poll you would likely perform some custom on- or off-chain data collection. Poll duration is also configured.
Copy
.poll((subscribers: ResourceId[]) => {
const sourceData: SourceData<YourDataType>[] = subscriber... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/decide-how-to-monitor-events/using-dialect-monitor-to-detect-events/learning-to-use-monitor-builder-supplying-data | [
" .poll((subscribers: ResourceId[]) => {const sourceData: SourceData<YourDataType>[] = subscribers.map((resourceId) => ({data: {cratio: Math.random(),healthRatio: Math.random(),resourceId,},groupingKey: resourceId.toString(),}),);return Promise.resolve(sourceData);}, Duration.fromObject({ seconds: 3 }))"
] |
Learning to Use Monitor Builder: Builder and Data Type | Actions & Alerts | Learning to Use Monitor Builder: Builder and Data Type
Monitor.builder (source
Copy
// Dialect SDK is configured and must be supplied
// below in builder props
const environment: DialectCloudEnvironment = 'development';
const dialectSolanaSdk: DialectSdk<Solana> = Dialect.sdk(
{
environment,
},
Solan... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/decide-how-to-monitor-events/using-dialect-monitor-to-detect-events/learning-to-use-monitor-builder-builder-and-data-type | [
"const environment: DialectCloudEnvironment = 'development';const dialectSolanaSdk: DialectSdk<Solana> = Dialect.sdk({environment,},SolanaSdkFactory.create({wallet: NodeDialectSolanaWalletAdapter.create(),}),);type YourDataType = {cratio: number;healthRatio: number;resourceId: ResourceId;};const monitor: Monitor<Yo... |
Learning to Use Monitor Builder: Data Transformation | Actions & Alerts | Learning to Use Monitor Builder: Data Transformation
During the transform step, streaming data from the previous step (eg poll, push) is operated on in succession to identify some event and trigger actions. In this snippet, a falling-edge of 0.5 on a number data type.
Copy
.transform<number, number>({
keys: ['... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/decide-how-to-monitor-events/using-dialect-monitor-to-detect-events/learning-to-use-monitor-builder-data-transformation | null |
Learning to Use Monitor Builder: Example 1 | Actions & Alerts | Learning to Use Monitor Builder: Example 1
This example emulates e2e scenario for monitoring some on- or off-chain resources for a set of subscribers and has 2 parts:
Client that emulates several users subscribing for dialect notifications from a monitoring service
Server that monitors some data for a set of monitor... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/decide-how-to-monitor-events/using-dialect-monitor-to-detect-events/learning-to-use-monitor-builder-example-1 | [
"import { Monitor, Monitors, Pipelines, ResourceId, SourceData } from '../src';import { Duration } from 'luxon';import {Dialect,DialectCloudEnvironment,DialectSdk,} from '@dialectlabs/sdk';import {Solana,SolanaSdkFactory,NodeDialectSolanaWalletAdapter} from '@dialectlabs/blockchain-sdk-solana';const environment: Di... |
Learning to Use Monitor Builder: Notify Step | Actions & Alerts | Learning to Use Monitor Builder: Notify Step
The dialectSdk notification sink is the standard notification sink. This data sink allows to unicast, multicast, or broadcast a message. Under the hood the SDK handles delivering the notification to any-and-all notification channels that the subscriber(s) has enabled.
Copy... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/decide-how-to-monitor-events/using-dialect-monitor-to-detect-events/learning-to-use-monitor-builder-notify-step | [
" .notify().dialectSdk(({ value }) => {return {title: 'dApp cratio warning',message: `Your cratio = ${value} below warning threshold`,};},{dispatch: 'unicast',to: ({ origin: { resourceId } }) => resourceId,},)"
] |
Monitor Hosting Options | Actions & Alerts | Monitor Hosting Options
Now that you have learned to implement a Dialect Monitor to detect and programmatically send notifications to your subscribers, you will need to host that monitor within a service.
If you already have a preferred infrastructure/framework for hosting services, you can simply choose to host and ... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/decide-how-to-monitor-events/using-dialect-monitor-to-detect-events/monitor-hosting-options | null |
Using Your Existing Event Detection | Actions & Alerts | Using Your Existing Event Detection
Option 2: Use Dialect's Open Source SDK to send Notifications From Your Existing Services
If you already have off-chain services that are detecting the events you care about, you can easily import the Dialect SDK into those services to send notifications to subscribers right as thos... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/decide-how-to-monitor-events/using-your-existing-event-detection | null |
Using Dialect Monitoring Service | Actions & Alerts | Using Dialect Monitoring Service
Dialect Reference Implementation
To wrap your Monitor within a monitoring service, see Dialect's default reference implementation at:
https://github.com/dialectlabs/monitoring-service-template
github.com
Monitoring Service Template Repository
Open Source Implementations of the Monitor... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/decide-how-to-monitor-events/using-dialect-monitor-to-detect-events/using-dialect-monitoring-service | null |
Use Dialect SDK to Send Notifications | Actions & Alerts | Use Dialect SDK to Send Notifications
Using the Dialect SDK to send notifications from within your backend services is essentially a two-step process:
Load your dapp from a Dialect SDK instance using your dapp's DIALECT_SDK_CREDENTIALS and configuration parameters.
Send dialect notifications at the place of event in... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/decide-how-to-monitor-events/using-your-existing-event-detection/use-dialect-sdk-to-send-notifications | null |
Advancing React Notifications | Actions & Alerts | Advancing React Notifications
Try a live example of the Dialect notification bell at https://alerts-example.dialect.to.
Previous
Use Dialect SDK to Send Notifications
Next
Using development environment
Last updated 3 months ago | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/advancing-react-notifications | null |
Using development environment | Actions & Alerts | Using development environment
We provide a free to use development environment to test your notifications. Here's example how to configure development environment:
Copy
'use client';
import '@dialectlabs/react-ui/index.css';
import { DialectSolanaSdk } from '@dialectlabs/react-sdk-blockchain-solana';
import {
... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/advancing-react-notifications/using-development-environment | [
"'use client';import '@dialectlabs/react-ui/index.css';import { DialectSolanaSdk } from '@dialectlabs/react-sdk-blockchain-solana';import {Icons,NotificationTypeStyles,NotificationsButton,} from '@dialectlabs/react-ui';const DAPP_ADDRESS = '...';export const DialectSolanaNotificationsButton = () => {return (<Dialec... |
Overriding icons | Actions & Alerts | Overriding icons
You can override icons according to your icons set in the app. Here's an example how to render a custom react component instead of built in icons:
Copy
// DialectNotificationComponent.tsx
'use client';
import '@dialectlabs/react-ui/index.css';
import { SVGProps } from 'react';
import { Dialec... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/advancing-react-notifications/overriding-icons | [
"'use client';import '@dialectlabs/react-ui/index.css';import { SVGProps } from 'react';import { DialectSolanaSdk } from '@dialectlabs/react-sdk-blockchain-solana';import {Icons,NotificationTypeStyles,NotificationsButton,} from '@dialectlabs/react-ui';const DAPP_ADDRESS = '...';Icons.Close = (props: SVGProps<SVGSVG... |
Customizing notifications channels | Actions & Alerts | Customizing notifications channels
Currently we support the following notifications channels:
wallet
telegram
email
By default all channels are enabled, but you can pass a set of different channels:
Copy
'use client';
import '@dialectlabs/react-ui/index.css';
import { DialectSolanaSdk } from '@dialectlabs/r... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/advancing-react-notifications/customizing-notifications-channels | [
"'use client';import '@dialectlabs/react-ui/index.css';import { DialectSolanaSdk } from '@dialectlabs/react-sdk-blockchain-solana';import {Icons,NotificationTypeStyles,NotificationsButton,} from '@dialectlabs/react-ui';const DAPP_ADDRESS = '...';export const DialectSolanaNotificationsButton = () => {return (<Dialec... |
Styling different notification types | Actions & Alerts | Styling different notification types
You'll probably have a multiple notification types for your app. By default all notifications are rendered with the same bell icon.
Default notification rendering
You can customize icon depending on notification types. For example you might want to have a green checkmark if notif... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/advancing-react-notifications/styling-different-notification-types | null |
Customizing notifications button | Actions & Alerts | Customizing notifications button
In some cases you might want to use your custom button component.
NotificationButton component can accept a function as a children with the following properties:
open - boolean value indicating if dialect modal is open
setOpen - react callback to control dialect modal open state
u... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/advancing-react-notifications/customizing-notifications-button | null |
Using your own modal component | Actions & Alerts | Using your own modal component
In some rare cases you might want to highly customize modal window. The easiest way is to use your own component.
NotificationButton component can accept a react component reference renderModalComponent with the following arguments:
open - boolean value indicating if dialect modal is ... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/advancing-react-notifications/using-your-own-modal-component | [
"'use client';import '@dialectlabs/react-ui/index.css';import { DialectSolanaSdk } from '@dialectlabs/react-sdk-blockchain-solana';import {Icons,NotificationTypeStyles,NotificationsButton,} from '@dialectlabs/react-ui';const DAPP_ADDRESS = '...';export const DialectSolanaNotificationsButton = () => {return (<Dialec... |
Styling Notifications widget | Actions & Alerts | Styling Notifications widget
You can style the following entities of the notifications component:
colors
border radius
font
modal container
Styling colors
Dialect defines a set of css variables, which are used to color the whole widget:
Copy
.dialect {
--dt-accent-brand: #09cbbf;
--dt-accent-error: #f62d2... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/advancing-react-notifications/styling-notifications-widget | null |
Using standalone notifications component | Actions & Alerts | Using standalone notifications component
In some rare cases you might want to just use Notifications component without built-in button and modal window. For example you might want to put component statically to the right side of your page. In this case you bring your own logic to display component and your own modal w... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/advancing-react-notifications/using-standalone-notifications-component | [
"'use client';import '@dialectlabs/react-ui/index.css';import { DialectSolanaSdk } from '@dialectlabs/react-sdk-blockchain-solana';import { Notifications } from '@dialectlabs/react-ui';const DAPP_ADDRESS = '...';export const DialectSolanaNotificationsButton = () => {return (<DialectSolanaSdk dappAddress={DAPP_ADDRE... |
Using custom wallet adapter | Actions & Alerts | Using custom wallet adapter
In some cases you might want to use a custom wallet adapter instead of @solana/wallet-adapter-react Here's how you can do it:
Copy
'use client';
import '@dialectlabs/react-ui/index.css';
import {
DialectSolanaSdk,
Environment,
} from '@dialectlabs/react-sdk-blockchain-solana'... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/advancing-react-notifications/using-custom-wallet-adapter | [
"'use client';import '@dialectlabs/react-ui/index.css';import {DialectSolanaSdk,Environment,} from '@dialectlabs/react-sdk-blockchain-solana';import {Icons,NotificationTypeStyles,NotificationsButton,ThemeType,} from '@dialectlabs/react-ui';import { useWallet } from '@solana/wallet-adapter-react';const DAPP_ADDRESS ... |
SDK | Actions & Alerts | SDK
This section describes how to interact with Dialect via an SDK.
Previous
Broadcast: Building Your Audience
Next
Typescript
Last updated 3 months ago | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/sdk | null |
Installation | Actions & Alerts | Installation
To start sending notifications with Dialect via it's Typescript SDK, first install @dialectlabs/sdk. This is the same installation as Messaging.
npm:
Copy
npm install @dialectlabs/sdk --save
# Solana notifications
npm install @dialectlabs/blockchain-sdk-solana --save
# Aptos notifications
npm in... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/sdk/typescript/installation | null |
Typescript | Actions & Alerts | Typescript
Installation
Configuration
Managing addresses
Subscribing to notifications
Load your dapp
Sending Dapp-to-User Messages
Managing notification types
Previous
SDK
Next
Installation
Last updated 3 months ago | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/sdk/typescript | null |
Configuration | Actions & Alerts | Configuration
All interactions with Dialect are done by first creating an sdk client, with some initial configuration. This configuration specifies:
What chains to use, such as Solana or Aptos.
What backends to use, including both the Dialect on chain Solana backend (v0), and/or the free, multi-chain Dialect cloud b... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/sdk/typescript/configuration | null |
Broadcast: Building Your Audience | Actions & Alerts | Broadcast: Building Your Audience
Many dapps wish to send product updates, community announcements, and other manually-crafted notifications to their users. Dialect offers an administrator dashboard for sending these announcements. Dapp administrators can connect to the dashboard here using your dapp's messaging keypa... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/broadcast-building-your-audience | null |
Subscribing to notifications | Actions & Alerts | Subscribing to notifications
Dialect allows users to manage subscriptions to receive notifications from dapps to specific addresses they have registered.
Addresses include not just their wallet via the Dialect protocol, but also email, Telegram, & SMS. To learn more about addresses, see the previous section on managi... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/sdk/typescript/subscribing-to-notifications | null |
Managing addresses | Actions & Alerts | Managing addresses
Dialect supports not only messaging via its web3 protocol, but also via email, Telegram, & SMS. Users manage addresss via the Dialect data service, where they may add, verify, update & remove addresses on file for these various channels.
Add a new address
Copy
const address = await sdk.wallet.addre... | https://docs.dialect.to/documentation/alerts/alerts-and-monitoring/sdk/typescript/managing-addresses | null |
README.md exists but content is empty.
- Downloads last month
- 2