Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
nft-openaction-kit
Advanced tools
Seamless integration of NFT platforms into the Lens protocol by enabling automatic detection and handling of NFT links within Lens publications.
The nft-openaction-kit package simplifies the process of integrating an NFT minting open action into Lens applications. This package has two core functionalities:
When a user posts a link to an NFT in a Lens Publication, this package will parse data from the URL and smart contracts to embed an NFT minting open action into the Lens Publication.
When a post appears in a Lens application feed with the NFT minting action attached, the app can use this package to populate metadata to appear on a UI and generate calldata to perform the transaction.
What is suported
What is not currently supported
detectAndReturnCalldata
. Detects the NFT platform and returns the calldata to be used in the post action.actionDataFromPost
. Returns the encoded calldata from Decent and UI data for the post action.IPlatformService
interface.
actionDataFromPost
is returingundefined
as the actionResponse from Decent is empty.
The route from Polygon to Zora is not configured in the Decent API.
Clone the repo
git clone https://github.com/0xnogo/nft-openAction-kit.git
Install NPM packages
yarn install
Build
yarn build
The package is not published. To use is locally, run
yarn link
in the root directory andyarn link nft-openaction-kit
in the project you want to use it.
Create a .env file in the root directory and add the following variables:
DECENT_API_KEY=api-key
Instantiate the NFTOpenActionKit
class and use the detectAndReturnCalldata
and actionDataFromPost
methods.
import { NftOpenActionKit } from "nft-openaction-kit";
// @param decentApiKey - string, required decent.xyz API key
// @param option fallbackRpcs - mapping of chainId to fallback RPC url
const nftOpenActionKit = new NftOpenActionKit({
decentApiKey: process.env.DECENT_API_KEY,
fallbackRpcs: {
[7777777]: "https://zora.g.alchemy.com/v2/<apiKey>",
[8453]: "https://base.g.alchemy.com/v2/<apiKey>",
},
});
detectAndReturnCalldata
method can be used by passing a URL, it will be parsed and if a supported NFT link is found the response type is a string
containing the open action calldata to be included within the post
, comment
, quote
, or mirror
transaction.const fetchCalldata = async () => {
try {
const result = await nftOpenActionKit.detectAndReturnCalldata({
contentURI: url, // url string to parse NFT data from
publishingClientProfileId: "10", // profileId, the owner address of this profile receives frontend mint rewards
});
console.log(result || "No calldata found");
} catch (err) {
console.log(err);
}
};
actionDataFromPost
when a publicaiton is rendered on a Lens feed to generate the cross-chain transaction calldata to be included with the act
transaction.const publication = {
profileId: "48935",
actionModules: ["0x99Cd5A6e51C85CCc63BeC61A177003A551953628"],
actionModulesInitDatas: [calldata],
pubId: "10",
};
try {
// Call the async function and pass the link
const result: ActionData = await nftOpenActionKit.actionDataFromPost({
post: publication,
profileId,
profileOwnerAddress,
senderAddress,
srcChainId,
quantity,
paymentToken,
executingClientProfileId,
mirrorerProfileId,
mirrorPubId,
sourceUrl,
});
} catch (error) {
console.log(error);
}
The
actionDataFromPost
function is accepting a subset of fields from Publication events (example event defined in https://github.com/wkantaros/lens-openAction).
The actionDataFromPost
or generateUIData
functions return a uiData
property. This object contains NFT metadata that can be used on a frontend display. All available properties are detailed below:
type UIData = {
platformName: string;
platformLogoUrl: string;
nftName: string;
nftUri: string;
nftCreatorAddress?: string;
tokenStandard: string;
dstChainId: number;
rawMetadataUri?: string;
zoraAdditional?: ZoraAdditional;
podsAdditional?: PodsAdditional;
};
type ZoraAdditional = {
name?: string;
description?: string;
image?: string;
animation_url?: string; // video or audio field, if one exists
content?: {
mime?: string;
uri?: string;
};
};
export type PodsAdditional = {
animation_url?: string; // podcast audio file
artwork?: {
kind?: string;
type?: string;
uri?: string;
};
collection?: string;
credits?: {
name?: string;
role?: string;
}[];
description?: string;
episodeNumber?: number;
episodeTitle?: string;
external_url?: string;
image?: string;
name?: string;
podcast?: string;
primaryMedia?: {
kind?: string;
type?: string;
uri?: string;
duration?: number;
};
properties?: {
Collection?: string;
Podcast?: string;
guest_1?: Record<string, unknown>;
host_1?: Record<string, unknown>;
host_2?: Record<string, unknown>;
[key: string]: unknown;
};
publishedAt?: string;
version?: string;
};
src/types/index.ts
:type SdkConfig = {
decentApiKey: string,
raribleApiKey?: string,
openSeaApiKey?: string,
};
src/DetectionEngine.ts
and add the new platform config following the type:type NFTPlatform = {
platformName: string,
platformLogoUrl: string,
urlPattern: RegExp,
urlExtractor: (url: string) => Promise<NFTExtraction | undefined>,
platformService: PlatformServiceConstructor,
};
src/platform
and add the platform service class. The class should implement the IPlatformService
interface.export type NFTPlatform = {
platformName: string,
platformLogoUrl: string,
urlPattern: RegExp,
urlExtractor: (url: string) => Promise<NFTExtraction | undefined>,
platformService: PlatformServiceConstructor,
apiKey?: string,
};
If an api key is required, make sure to add it in the
DetectionEngine
class and handle it in theinitializePlatformConfig
function. The Rareble detection is an example of how to handle an api key.
src/platform
and add the platform service class. The class should implement the IPlatformService
interface.interface IPlatformService {
platformName: string;
getMinterAddress(
nftDetails: NFTExtraction,
mintSignature: string
): Promise<string>;
getMintSignature(
nftDetails: NFTExtraction,
ignoreValidSale?: boolean
): Promise<string | undefined>;
getUIData(
signature: string,
contract: string,
tokenId: bigint,
dstChainId: bigint,
sourceUrl?: string
): Promise<UIData | undefined>;
getPrice(
contractAddress: string,
nftId: bigint,
signature: string,
userAddress: string,
unit?: bigint,
sourceUrl?: string
): Promise<bigint | undefined>;
getArgs(
contractAddress: string,
tokenId: bigint,
senderAddress: string,
signature: string,
price: bigint,
quantity: bigint,
profileOwnerAddress: string,
sourceUrl?: string
): Promise<any[]>;
}
FAQs
Seamless integration of NFT platforms into the Lens protocol by enabling automatic detection and handling of NFT links within Lens publications.
The npm package nft-openaction-kit receives a total of 430 weekly downloads. As such, nft-openaction-kit popularity was classified as not popular.
We found that nft-openaction-kit demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.