truffle-hdwallet-provider - HD Wallet-enabled Web3 provider

  •        1098

HD Wallet-enabled Web3 provider. Use it to sign transactions for addresses derived from a 12-word mnemonic.You can use this provider wherever a Web3 provider is needed, not just in Truffle. For Truffle-specific usage, see next section.

https://github.com/trufflesuite/truffle-hdwallet-provider#readme

Dependencies:

bip39 : ^2.2.0
ethereumjs-wallet : ^0.6.0
web3 : ^0.18.2
web3-provider-engine : ^8.4.0

Tags
Implementation
License
Platform

   




Related Projects

bitcore-wallet-service - A multisig, HD wallet service. Used by Copay.

  •    Javascript

A Multisig HD Bitcore Wallet Service.Bitcore Wallet Service facilitates multisig HD wallets creation and operation through a (hopefully) simple and intuitive REST API.

eth-lightwallet - Lightweight JS Wallet for Node and the browser

  •    Javascript

A minimal ethereum javascript wallet. LightWallet is a HD wallet that can store your private keys encrypted in the browser to allow you to run Ethereum dapps even if you're not running a local Ethereum node. It uses BIP32 and BIP39 to generate an HD tree of addresses from a randomly generated 12-word seed.

node-oidc-provider - OpenID Provider(OP) implementation for node

  •    Javascript

oidc-provider is an OpenID Provider implementation of OpenID Connect. It allows to export a complete mountable or standalone OpenID Provider implementation. This implementation does not dictate a fixed data models or persistence store, instead, you must provide adapters for these. A generic in memory adapter is available to get you started as well as feature-less dev-only views to be able to get off the ground. The following specifications are implemented by oidc-provider. Note that not all features are enabled by default, check the configuration section on how to enable them.

terraform-provider-google - Terraform Google Cloud Platform provider

  •    Go

See the Google Provider documentation to get started using the Google provider. We recently introduced the google-beta provider. See Provider Versions for more details on how to use google-beta.

terraform-provider-oci - Terraform Oracle Cloud Infrastructure provider

  •    Go

The OCI Terraform Provider is now available for automatic download through the Terraform Provider Registry. For more information on how to get started view the documentation and setup guide. Note: You may use any version 1.8 or above to build the provider. However, the goimports, go vet, and gofmt code checks will only pass when using version 1.11.


terraform-provider-aws - Terraform AWS provider

  •    Go

If you're building the provider, follow the instructions to install it as a plugin. After placing it into your plugins directory, run terraform init to initialize it. Documentation about the provider specific configuration options can be found on the provider's website. If you wish to work on the provider, you'll first need Go installed on your machine (version 1.11+ is required). You'll also need to correctly setup a GOPATH, as well as adding $GOPATH/bin to your $PATH.

terraform-provider-helm - Terraform Helm provider

  •    Go

This is a Helm provider for Terraform. The provider manages the installed Charts in your Kubernetes cluster, in the same way of Helm does, through Terraform. It will also install Tiller automatically if it is not already present.

terraform-provider-kubernetes - Terraform Kubernetes provider

  •    Go

In order to prevent breaking changes and migration of user-created resources, resources included in this provider will be limited to v1 APIs and not alpha or beta. You can find v1 resources in the Kubernetes API documentation for the appropriate version of Kubernetes. If you wish to work on the provider, you'll first need Go installed on your machine (version 1.9+ is required). You'll also need to correctly setup a GOPATH, as well as adding $GOPATH/bin to your $PATH.

pact-ruby - Enables consumer driven contract testing, providing a mock service and DSL for the consumer project, and interaction playback and verification for the service provider project

  •    Ruby

Define a pact between service consumers and providers, enabling "consumer driven contract" testing. Pact provides a fluent API for service consumers to define the HTTP requests they will make to a service provider and the HTTP responses they expect back. These expectations are used in the consumer specs to provide a mock service provider. The interactions are recorded, and played back in the service provider specs to ensure the service provider actually does provide the response the consumer expects.

Hybrid Provider / Hybrid Profiler / Hybrid Roller

  •    

The Hybrid Provider allows SharePoint sites to simultaneously authenticate SQL and AD users. This is different from extending web apps and creating multiple zones. The aforementioned "supported" method to dual authentication requires managing multiple web apps and doesn't allow

Code-First Membership / Role Provider

  •    

Code-First Membership / Role Provider is built using C# and allows for drop-in type usage / abstraction unlike other code-fist options at the moment.

Single Sign On - 2.0 Web Service Membership Provider

  •    DotNet

In short, this is simply a pass-through web service membership provider and role provider library. I've taken advantage of the 2.0 membership provider model to allow pre-existing applications to easily integrate this library. The idea is to have one centrally hosted asp.net we...

WebIntents - A client side service discovery and execution model.

  •    Javascript

Web Intents is a discovery mechanism and extremely light-weight RPC system between web apps, modeled after the similarly-named system in Android. An Intent is an action to be performed by a provider. Intents provides a declarative syntax that allows providers to list the Intents they handle and a registration system that enumerates available providers. A client requests an Intent be handled, the User Agent allows the user to select which provider to use, and the provider performs the action of the Intent, possibly using data passed as input in the Intent. The provider may return data as output to the client. When browsers start to implement this natively the Shim will defer all its functionality to the native interface.

vagrant-vsphere - VMware vSphere provider for Vagrant

  •    Ruby

This is a Vagrant 1.6.4+ plugin that adds a vSphere provider to Vagrant, allowing Vagrant to control and provision machines using VMware. New machines are created from virtual machines or templates which must be configured prior to using this provider. This provider is built on top of the RbVmomi Ruby interface to the vSphere API.

android-DownloadableFonts

  •    Java

This sample demonstrates how to use the Downloadable Fonts feature introduced in Android O. Downloadable Fonts is a feature that allows apps to request a certain font from a provider instead of bundling it or downloading it themselves. This means, there is no need to bundle the font as an asset. The parameters ProviderAuthority, ProviderPackage are given by a font provider, in the case above uses Google Play Services as a font provider. The third parameter is a query string about the requested font. The syntax of the query is defined by the font provider.

terraform-provider-azurerm - Terraform provider for Azure Resource Manager

  •    Go

Further usage documentation is available on the Terraform website. If you wish to work on the provider, you'll first need Go installed on your machine (version 1.11+ is required). You'll also need to correctly setup a GOPATH, as well as adding $GOPATH/bin to your $PATH.

smart-home-nodejs - A sample of the Smart Home device control APIs in Actions on Google

  •    HTML

This sample contains a fully functioning example of a Smart Home provider cloud service designed to work with Actions on Google. This can be used with a Actions Console project to create an Action interface to your IoT devices. This sample includes everything you need to get started, including a mocked user authentication service with sample users and a user web portal to demonstrate the user experience when controlling their lights with your action. An example of a Smart Home IoT cloud engine is stored in smart-home-provider. This consists of both the main smart-home-provider-cloud.js main web service, as well as the web portal used to interact with virtual devices in frontend/. smart-home-provider-cloud.js is the entry point to the Node.js Express app that runs the IoT cloud service, and handles authentication, and ultimately handles requests from the Google Assistant.

buford - A push notification delivery engine for the new HTTP/2 APNS service.

  •    Go

Apple Push Notification (APN) Provider library for Go 1.6 and HTTP/2. Send remote notifications to iOS, macOS, tvOS and watchOS. Buford can also sign push packages for Safari notifications and Wallet passes. Please see releases for updates.