![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@lit-protocol/wrapped-keys
Advanced tools
This submodule is used for Wrapped Keys which allows you to import any existing keys. You can also export these keys to the user. These keys are encrypted and stored in a DynamoDB instance managed by Lit. You can use functions to sign a message/transactio
This submodule is used for Wrapped Keys which allows you to import any existing keys. You can also export these keys to the user. These keys are encrypted and stored in a DynamoDB instance managed by Lit. You can use functions to sign a message/transaction within a Lit Action as even broadcast it to the required blockchain.
yarn add @lit-protocol/wrapped-keys
By default, this package uses IPFS CIDs to indicate the Lit Actions involved, which tells LIT nodes to fetch our internally managed and IPFS-published LIT action source code from IPFS internally, when they receive requests from your users.
This behaviour can be modified by calling config.setLitActionsCode({ litActionRepository })
and providing your own source code for LIT actions, which allows you to either embed your LIT action source code into your app bundle or even fetch it dynamically during app load.
When setting an explicit Lit Action source code repository, Lit Action source code will be sent to the LIT nodes in each request from your users, instead of relying on the nodes fetching the code from IPFS.
This can provide performance improvements in some circumstances due to the variable nature of IPFS performance, but with an added overhead in bandwidth used for each request your users make, bundle size and/or app load time depending on your use case.
To use LIT-provided Lit Actions and bundle their source code into your app, use @lit-protocol/wrapped-keys-lit-actions
or define your own LIT action source code dictionary,
Example using LIT-provided action source code:
import { litActionRepository } from '@lit-protocol/wrapped-keys-lit-actions';
import { config, api } from '@lit-protocol/wrapped-keys';
config.setLitActionsCode({ litActionRepository });
FAQs
This submodule is used for Wrapped Keys which allows you to import any existing keys. You can also export these keys to the user. These keys are encrypted and stored in a DynamoDB instance managed by Lit. You can use functions to sign a message/transactio
We found that @lit-protocol/wrapped-keys 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.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.