Ethereum Light client with React – Ko – Medium

Ethereum Light client with React  #react #ethereum #reactjs

  • { ssl_fc }frontend wwws mode http bind :443 ssl crt /etc/haproxy/certs/You Cert.pem timeout client 1h tcp-request inspect-delay 500ms tcp-request content accept if HTTP default_backend privatenetwork_backend acl is_privatenetwork hdr_end(host) -i Your domain use_backend privatenetwork_backend if is_privatenetworkbackend privatenetwork_backend mode http option forwardfor option http-server-close option forceclose no option httpclose balance roundrobin option…
  • web3 is official Javascript library for ethereum.npm install –save eth-lightwalletnpm install –save hooked-web3-providernpm install –save web3# Or you may do just npm installA bit of hackIn your Javascript file,// step 1: import web3, eth-lightwallet, and hooked-web3-providerimport Web3 from ‘web3’import lightwallet from ‘eth-lightwallet’import HookedWeb3Provider from ‘hooked-web3-provider’// step 2: you may need to…
  • It’s a bit troublesome though because every time I add new module, I need to do “npm install” at eth-lightwallet directory.Now you are ready to create UIFirst step is creating keystore or wallet with keystore.
  • # I pick the name wallet because in the original document, the term keystore is used both medhod name and generated wallet with keystore and bit confusing.let wallet# get pwDerivedKey password, (err, pwDerivedKey) = { if (err){ console.log(“err 1:”, err) } # goto step.2Step 2 is generate address.
  • # step.2: add new 3 connect to our node (rpc server) with hooked-web3-provider# step.3: prepare providervar web3Provider = new HookedWeb3Provider({ host: “https://your rpc server”, transaction_signer: wallet});const web3 = new Web3(web3Provider);Here you need hooked-web3-provider.

Light client is an ethereum client which keeps only keys. You can check accurate definition here. Traditionally in blockchain world, everyone keep same databases. That’s why we can trust entire…
Continue reading “Ethereum Light client with React – Ko – Medium”

How to use React’s Provider Pattern

How to use React's Provider Pattern  #reactjs #webdev

  • Therefore you could use React’s context to give every component access to the colored theme.
  • That way every component that needs to be styled according to the colored theme could get the necessary information from React’s context object.
  • You have the Provider component that makes properties accessible in React’s context and components that consume the context.
  • This Provider component uses React’s context to pass down the state implicitly.
  • You provide the state to your component as props, the component wraps it into React’s context and all child components can access the state by using a higher order component such as from the react-redux library.

This article gives you a walkthrough for React’s provider pattern. After reading it, you should be able to implement…
Continue reading “How to use React’s Provider Pattern”

Now that it’s okay to use @reactjs again, I can say: I’ve been working on this @WordPress + React thing for awhile

  • Postlight’s Headless WordPress + React Starter Kit is an automated toolset that will spin up two things: – – The following setup will get WordPress running locally on your machine, along with the WordPress plugins you’ll need to create and serve custom data via the WP REST API.
  • To install and start WordPress, run the following command: – – When that completes successfully, the WordPress REST API will be available at http://localhost:8080.
  • To import data and media from a live WordPress install locally, use Migrate DB Pro.
  • At this point you can start setting up custom fields, and if necessary, creating custom REST API endpoints in the Postlight Headless WordPress Starter theme.
  • Once you have Docker installed on your computer, you can run the container locally using this command:

headless-wp-starter – 🔪 WordPress + React: a starter kit
Continue reading “Now that it’s okay to use @reactjs again, I can say: I’ve been working on this @WordPress + React thing for awhile”

8 things to learn in React before using Redux

8 things to learn in #ReactJS before using #Redux:

  • A component can manage a whole lot of state, pass it down as props to its child components and pass a couple of functions along the way to enable child components to alter the state in the parent component again.
  • Component A is the only component that manages local state but passes it down to its child components as props.
  • In addition, it passes down the necessary functions to enable B and C to alter its own state in A.

    Now, half of the local state of component A is consumed as props by component C but not by component B.

  • When you lift the local state management down to component C, all the necessary props don’t need to traverse down the whole component tree.
  • When a library such as Redux “connects” its state managements layer with React’s view layer, you will often run into a higher order component that takes care of it (connect HOC in react-redux).

Facts about React that should be known before using Redux (or MobX). Most important: Learn React first, then opt-in Redux…
Continue reading “8 things to learn in React before using Redux”

Stop Managing CSS – Charlie Hulcher – Medium

Stop Managing CSS  #cssinjs #react #styledcomponents #css #http2 #reactjs

  • Stop Managing CSSA response to Managing CSS JS in a HTTP/2 WorldThis article on getting great performance out of HTTP/2 would have excited me hugely before.
  • Sane structure and tooling around SCSS that allows for the best loading benefits with HTTP/2 is definitely the future when your styles are separate from everything else.I believed in separating styles, behavior, and structure for a long time.
  • Keep style alongside behavior and structure.Coming from that context, reading about the right way to manage CSS felt like watching exciting evolution for a dated paradigm.
  • A cleaner design for a horse harness is a beautiful thing but doesn’t beat the engine.Solving the problem of chunked CSS delivery in order to get performance benefits from HTTP/2 sounds to me like reinventing the wheel from what you’re probably already doing.
  • Why rebuild that process in parallel for CSS?The core problem comes down to managing CSS inclusion/exclusion from the project through a human process.

This article on getting great performance out of HTTP/2 would have excited me hugely before. Sane structure and tooling around SCSS that allows for the best loading benefits with HTTP/2 is definitely…
Continue reading “Stop Managing CSS – Charlie Hulcher – Medium”


  • React, MobX, React-Router and Webpack boilerplate with async routes.
  • This boilerplate is also ready for deploying your app to Heroku.
  • Components are now loaded async with react-router-loader and the store is injected via MobX Provider.

React, MobX, React-Router, MobX-Router and Webpack (heroku-ready) boilerplate with async routes.
Continue reading “react-mobx-react-router-boilerplate”