Security News
JSR Working Group Kicks Off with Ambitious Roadmap and Plans for Open Governance
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
@venly/web3-provider
Advanced tools
Venly enabled Web3 Provider for the web
The Venly Web3 provider is a smart wrapper around the existing Web3 Ethereum JavaScript API.
If you already have an application running using web3 technology, you can make use of this wrapper to leverage the full potential of Venly Wallet API. Your existing infrastructure is just one code block away from being Venly Wallet Enabled.
Install and import the module in your project
npm i @venly/web3-provider
import { VenlyProvider } from "@venly/web3-provider";
Alternatively, you can load our script from one of the following CDNs
<script src="https://unpkg.com/@venly/web3-provider/umd/index.js"></script>
<script src="https://cdn.jsdelivr.net/npm/@venly/web3-provider/umd/index.js"></script>
const Venly = new VenlyProvider();
The VenlyProvider object is the gateway for creating the web3 wrapper and fully integrates Venly Connect.
const options: VenlyProviderOptions = {
clientId: 'YOUR_CLIENT_ID',
environment: 'sandbox', //optional, defaults to production
secretType: SecretType.ETHEREUM, //optional, defaults to ETHEREUM
windowMode: WindowMode.POPUP, //optional, defaults to POPUP
bearerTokenProvider: () => 'obtained_bearer_token', //optional
skipAuthentication: false //optional, defaults to false
};
const provider = await Venly.createProvider(options);
const web3 = new Web3(provider);
The web3 instance now works as if it was injected by parity or metamask. You can fetch your wallets or sign transactions and messages.
If you provide your own implementation of bearerTokenProvider
, the web3 provider will not attempt to obtain an authentication code, but rather use the one provided by you.
Use the Web3Provider class to wrap our existing Web3-compatible provider and expose it as an ethers.js Provider. (Requires ethers.js v5)
const options = {
clientId: 'YOUR_CLIENT_ID'
};
const provider = await Venly.createProvider(options);
const ethers = new ethers.providers.Web3Provider(provider);
After initializing the Venly Provider, an instance of VenlyConnect is added to the Venly object. As a result, it's possible to call Venly Connect natively.
Venly.connect.getProfile();
The full documentation for Venly Connect can be found here: https://docs.venly.io/widget/widget/introduction
Many of required dependencies are not normally included in browser builds (namely the node built-in modules such as crypto
, buffer
, util
etc). If you are having build issues you can try the following bundler configs to resolve these dependency issues:
React App Rewired provides a simple way to override webpack config which is obfuscated in Create React App built applications.
Add the following dev dependencies:
npm i --save-dev assert buffer crypto-browserify stream-http https-browserify process stream-browserify url browserify-zlib
OR
yarn add assert buffer crypto-browserify stream-http https-browserify process stream-browserify url browserify-zlib -D
Create a config-overrides.js
file in the root directory:
const webpack = require('webpack')
module.exports = function override(config) {
const fallback = config.resolve.fallback || {}
Object.assign(fallback, {
assert: require.resolve('assert'),
buffer: require.resolve('buffer'),
crypto: require.resolve('crypto-browserify'),
http: require.resolve('stream-http'),
https: require.resolve('https-browserify'),
process: require.resolve('process/browser'),
stream: require.resolve('stream-browserify'),
url: require.resolve('url'),
zlib: require.resolve('browserify-zlib')
})
config.resolve.fallback = fallback
config.plugins = (config.plugins || []).concat([
new webpack.ProvidePlugin({
process: 'process/browser',
Buffer: ['buffer', 'Buffer']
})
])
config.ignoreWarnings = [/Failed to parse source map/]
config.module.rules.push({
test: /\.(js|mjs|jsx)$/,
enforce: 'pre',
loader: require.resolve('source-map-loader'),
resolve: {
fullySpecified: false
}
})
return config
}
We've created two examples of the Web3 Provider in our demo application.
One only checks authentication and shows the login form after the user clicks a button:
The other checks if a user is logged in on page load. If not, it shows the login button, otherwise it fetches the users' wallets:
Not sure yet what Venly is all about? Be sure to check out our website: https://www.venly.io/
FAQs
Venly enabled Web3 Provider for the web
The npm package @venly/web3-provider receives a total of 203 weekly downloads. As such, @venly/web3-provider popularity was classified as not popular.
We found that @venly/web3-provider demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 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
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.