KC Chng (CEO)
Code Reviewer selected and to be announced in the coming week
As mentioned in our last update, we began our search for an appropriate code reviewer to go through Digix’s core contracts. As our codebase is inherently complex, the quicker our code reviewer can become well versed with our codebase and contract design, the quicker they can begin a full scale security audit for Digix core contracts. A cursory code review is likely to take up the next 2–3 weeks, again dependent on whether any glaring bugs are found, with a full scale audit occurring after. If no glaring issues are found, we should be ready for beta launching on the main net after security audits. As always, we will keep our supporters informed of the progress.
A well known development house has kindly agreed to look through our code and we will make a separate announcement early next week once details are finalized. This particular development house’s experience in building complicated software architecture on Ethereum makes them a perfect fit to look through Digix’s code base, and I am fully confident of their ability to assist us through to our production phase.
Feedback on the ETC refund proposal
The proposal has been out for 4 days, and the general consensus is that it is welcomed without much contention. We will leave the proposal running and open for comment for the next 2 weeks and republish an updated version based on public feedback.
For anyone wishing to comment on the ETC proposal, please head to
https://www.reddit.com/r/digix/comments/60ymcz/digixdao_etc_withdrawal_proposal_v10_mar_22_2017/ and leave your comments.
Some token holders are calling for a refund of ETC to be done by April 15 to be ahead of TheDao’s ETC refund, however, with the relaunch of DGX 2.0 being a priority at this stage, the refund of ETC will unlikely occur before April 15.
Anthony Eufemio (CTO)
Development work on DigixCore Assets continues. This weeks’s focus is on integrating the PoA process with the marketplace. The idea is to tightly couple the marketplace and physical gold bar redemption process with the Core 2 contracts. The purpose of this integration is to have the proper regulatory compliance mechanism in place for KYC/AML.
Chris Hitchcott (Core Dev)
Aside from helping out with the withdrawal proposal and presenting at SG innovate, I’ve been working on solving a particular use case with the PoA UI — the issue is that for each transaction we want a single IPFS hash for verifying the actions of the various backoffice users (vendors, custodians, auditors).
I have implemented a completely in-browser process of allowing these users to import a combination of PDFs, JPEGs and PNGs, and then having them automatically “stitched” together into a single PNG file. I leveraged the PDF.js library for separating out the individual pages from a PDF, converting them to image data, and combining them (along with other images) into a canvas element, watermarking each page with a timestamp, and then exporting the stitched-image canvas data as a PNG buffer.
From an end user perspective, it looks just the same as the UI demo released last week, but with this additional functionality, it means that users won’t need to worry about the format of the documents they upload, as they can just throw multiple differently-formatted documents at the UI, and they will be all converted automatically in-browser into the correct format before being uploaded to IPFS (and the image will also have additional metadata attached to the image itself in the form of a watermark).
- 81a1042 — [maint] Refactor (change contract naming convention and resolver keys)
- d873f67 — [wip] refactor and rename
- da34eaf — [wip] renaming and refactor
- fd64f2e — [maint] add new partnerships
- faeb702 — [wip] implement pdf/image processing into digix_assets dapplet w/ IPFS
- 3962819 — [wip] basic pdf & image converting functionality
- 8b91d53 — [maint] update linting