What it looks like to a non dev (me) is possibly some of their MVP code (guessing that from the "rinkeby" reference in the code) for handling ethereum requests along with an example of how fees and token burn are going to work.
I think there could be some pretty mad stacks of green paper on the way.
This repo appears to be the foundation of their release management tooling.
These files are "artefacts" - the output of automated build processes. For example when you create a Solidity file, you generate a JSON-formatted ABI file which describes the functionality of the contract. This repository is for storing those artefacts.
So we aren't looking at new code/features here, but we are looking at a team that knows what they are doing when it comes to agile development methods. This is an unsexy but necessary step on the path to main net release.
4
u/Jimmyl101 REQMarine Jan 25 '18
New section on the Request Network Github, I'm sorry I doubted the work of the team earlier in the week.