gringo - Alternative full Grin node on Golang (implementation of the MimbleWimble protocol) https://github

  •        13

Golang (Go) implementation of full Grin (grin network) node. Development status: frozen (highly unstable grin's consensus & protocol).

https://github.com/dblokhin/gringo

Tags
Implementation
License
Platform

   




Related Projects

grin - Minimal implementation of the MimbleWimble protocol.

  •    Rust

To learn more, read our introduction to MimbleWimble and Grin. Grin is still an infant, much is left to be done and contributions are welcome (see below). Check our mailing list archives for the latest status.

GrinGo

  •    C++

GrinGo is now part of Potassco http://potassco.sourceforge.net/

Potassco

  •    

Potassco, the Potsdam Answer Set Solving Collection bundles tools for Answer Set Programming developed at the University of Potsdam, among them, the answer set solver clasp, the grounder gringo, and their combinations clingo and iclingo.

redis_failover - redis_failover is a ZooKeeper-based automatic master/slave failover solution for Ruby

  •    Ruby

redis_failover provides a full automatic master/slave failover solution for Ruby. Redis does not currently provide an automatic failover capability when configured for master/slave replication. When the master node dies, a new master must be manually brought online and assigned as the slave's new master. This manual switch-over is not desirable in high traffic sites where Redis is a critical part of the overall architecture. The existing standard Redis client for Ruby also only supports configuration for a single Redis server. When using master/slave replication, it is desirable to have all writes go to the master, and all reads go to one of the N configured slaves. This gem (built using ZK) attempts to address these failover scenarios. One or more Node Manager daemons run as background processes and monitor all of your configured master/slave nodes. When the daemon starts up, it automatically discovers the current master/slaves. Background watchers are setup for each of the redis nodes. As soon as a node is detected as being offline, it will be moved to an "unavailable" state. If the node that went offline was the master, then one of the slaves will be promoted as the new master. All existing slaves will be automatically reconfigured to point to the new master for replication. All nodes marked as unavailable will be periodically checked to see if they have been brought back online. If so, the newly available nodes will be configured as slaves and brought back into the list of available nodes. Note that detection of a node going down should be nearly instantaneous, since the mechanism used to keep tabs on a node is via a blocking Redis BLPOP call (no polling). This call fails nearly immediately when the node actually goes offline. To avoid false positives (i.e., intermittent flaky network interruption), the Node Manager will only mark a node as unavailable if it fails to communicate with it 3 times (this is configurable via --max-failures, see configuration options below). Note that you can (and should) deploy multiple Node Manager daemons since they each report periodic health reports/snapshots of the redis servers. A "node strategy" is used to determine if a node is actually unavailable. By default a majority strategy is used, but you can also configure "consensus" or "single" as well.

node-gyp - Node.js native addon build tool

  •    Python

node-gyp is a cross-platform command-line tool written in Node.js for compiling native addon modules for Node.js. It bundles the gyp project used by the Chromium team and takes away the pain of dealing with the various differences in build platforms. It is the replacement to the node-waf program which is removed for node v0.8. If you have a native addon for node that still has a wscript file, then you should definitely add a binding.gyp file to support the latest versions of node.Multiple target versions of node are supported (i.e. 0.8, ..., 4, 5, 6, etc.), regardless of what version of node is actually installed on your system (node-gyp downloads the necessary development files or headers for the target version).


node-fibers - Fiber/coroutine support for v8 and node.

  •    C++

Fibers, sometimes called coroutines, are a powerful tool which expose an API to jump between multiple call stacks from within a single thread. This can be useful to make code written for a synchronous library play nicely in an asynchronous environment. Note: node-fibers uses node-gyp for building. To manually invoke the build process, you can use node-gyp rebuild. This will put the compiled extension in build/Release/fibers.node. However, when you do require('fibers'), it will expect the module to be in, for example, bin/linux-x64-v8-3.11/fibers.node. You can manually put the module here every time you build, or you can use the included build script. Either npm install or node build -f will do this for you. If you are going to be hacking on node-fibers, it may be worthwhile to first do node-gyp configure and then for subsequent rebuilds you can just do node-gyp build which will be faster than a full npm install or node-gyp rebuild.

nodock - Docker Compose for Node projects with Node, MySQL, Redis, MongoDB, NGINX, Apache2, Memcached, Certbot and RabbitMQ images

  •    Shell

The docker Node.js image is very simple, you give it an entrypoint and it runs it. This is fine for very simple/small scripts but for larger projects you'll probably want something a bit more robust. The goal of NoDock is to provide a complete environment for your node project: Node.js service(s), databases, web servers, queues, etc. while doing the "wiring" for you.

why-is-node-running - Node is running but you don't know why? why-is-node-running is here to help you

  •    Javascript

Node is running but you don't know why? why-is-node-running is here to help you.You can also run why-is-node-running standalone if you don't want to include it inside your code. Sending SIGUSR1 signal to the process will produce the log.

avn - Automatic Version Switching for Node

  •    Javascript

Now when you cd into a directory with a .node-version file, avn will automatically detect the change and use your installed version manager to switch to that version of node. What goes in your .node-version file? A semver version number corresponding to the version of Node.js that your project uses. We don't recommend using all of these tools to manage your versions of node, but feel free to install all of them. They won't conflict with each other.

heroku-cra-node - How to use create-react-app with a custom Node server on Heroku

  •    Javascript

A minimal example of using a Node backend (server for API, proxy, & routing) with a React frontend. Includes a minimal Node Cluster implementation to parallelize the single-threaded Node process across the available CPU cores.

nodenv - Manage multiple NodeJS versions.

  •    Shell

Use nodenv to pick a Node version for your application and guarantee that your development environment matches production. Put nodenv to work with npm for painless Node upgrades and bulletproof deployments. Powerful in development. Specify your app's Node version once, in a single file. Keep all your teammates on the same page. No headaches running apps on different versions of Node. Just Works™ from the command line. Override the Node version anytime: just set an environment variable.

babel-watch - Reload your babel-node app on JS source file changes. And do it fast.

  •    Javascript

Reload your babel-node app on JS source file changes. And do it fast. If you're tired of using babel-node together with nodemon (or similar solution). The reason why the aforementioned setup performs so badly is the startup time of babel-node itself. babel-watch only starts babel in the "master" process where it also starts the file watcher. The transpilation is performed in that process too. On file-watcher events, it spawns a pure node process and passes transpiled code from the parent process together with the source maps. This allows us to avoid loading babel and all its deps every time we restart the JS script/app.

node-steam-user - Improved SteamUser handler for node-steam 1.0.0 and later

  •    Javascript

SteamUser is a handler module for node-steam version 1.0.0 or greater. It also works with node-steam-client. It's designed to be a self-contained module which provides all the functionality expected of a Steam user client.

node-boilerplate - Everything you need to get started on a Node

  •    Javascript

Requires Node v0.6.6 (or newer) node-boilerplate takes html-boilerplate, express, connect, jade and Socket.IO and organizes them into a ready to use website project. It's a fast way to get working on your Node website without having to worry about the setup. It takes care of all the boring parts, like setting up your views, 404 page, 500 page, getting the modules organized, etc... This will copy down all of the boilerplate files, organize them appropriately and init a fresh new git repository within which you can build your next big thing.

node-v0.x-archive - Moved to https://github.com/nodejs/node

  •    

This repository is an archive of Node.js before the move to nodejs/node.It still contains issues and pull requests that are relevant to Node versions v0.10 and v0.12, and that were opened before the move to nodejs/node. New issues and pull requests, for all branches, should be opened at nodejs/node. New issues and pull requests opened here will automatically be rejected.

node-pre-gyp - Node.js tool for easy binary deployment of C++ addons

  •    Javascript

node-pre-gyp stands between npm and node-gyp and offers a cross-platform method of binary deployment.For a hello world example of a module packaged with node-pre-gyp see https://github.com/springmeyer/node-addon-example and the wiki for real world examples.

gnode - Run node with ES6 Generators, today!

  •    Javascript

gnode is a very light wrapper around your node executable that ensures ES6 Generator support, even on versions of node that do not support ES6 Generators natively.You use it exactly like the regular node executable, except that you do not need to pass the --harmony-generators flag. That is where the magic happens.

node-promise - Promise utilities for Node

  •    Javascript

MIT License. The node-promise project provides a complete promise implementation. Promises provide a clean separation of concerns between asynchronous behavior and the interface so asynchronous functions can be called without callbacks, and callback interaction can be done on the generic promise interface. The node-promise package provides just a promise implementation, however, https://github.com/kriszyp/promised-io is recommended for more complete promise-based IO functionality. The promised-io includes the promise implementation from node-promise, as well as wrappers around Node's filesystem and other system I/O APIs for consistent promise-based interaction.

node-red-contrib-chatbot - Visually build a full featured chat bot for Telegram, Facebook Messenger and Slack with Node-RED

  •    HTML

With RedBot you can visually build a full featured chat bot for Telegram, Facebook Messenger and Slack with Node-RED. Almost no coding skills required. Node-RED is a tool for wiring together hardware devices, APIs and online services in new and interesting ways.

node-persist - Super-easy persistent data structures in Node.js

  •    Javascript

Node-persist doesn't use a database. Instead, JSON documents are stored in the file system for persistence. Because there is no network overhead, node-persist is just about as fast as a database can get. Node-persist uses the HTML5 localStorage API, so it's easy to learn. This is still a work in progress. Send pull requests please.