# **GildLab Update 1 - 1 March - 10 April 2023**

The focus has been on Semi-Fungible Token system testing, usability and UI improvements; as well as hosting overhauls.

## Hosting summary

### Hosting upgrades
* IPFS nodes have been updated to latest versions of IPFS network
* We've introduced some additional static IPs to our hardware
* Hosting is now much faster and less buggy for uploaded files

### Hosting performance
The multiregion IPFS node approach is proving to work well, we had a few temporary connectivity drops from individual nodes, but uninterrupted access to pinned data overall according to our monitoring.

| 30D | 7D |
| -------- | -------- |
|  |  |

To check uptime: https://upptime.gildlab.xyz/

## Application summary

* Prompts have now been added (with the background blurred out) to clearly guide the users from each transaction through to it’s successful completion.
* Further testing has resulted in a more resilient system; with buttons that aren’t ready to be clicked, disabled, pages streamlined and clear waiting times.
* UI updates have been made to the pages: ‘Roles’, ‘Members’, ‘Mint/Redeem’ and the ‘New asset class schema’ (previously named ‘New schema’).
* The 'Members' screen has been streamlined for more efficient data input. The ‘Assign tier button’ and the edit pencil icons have been removed.
* Everywhere that was titled ‘Options’ is now titled ‘Amount’ including ‘Audit history’ and the ‘Mint/Redeem’ page.
* The 'New Schema' button found on the ‘Mint’ screen that guides users to input schemas has been renamed to 'New asset class'. This connects to 'New asset class schema' Where the new asset classes are promptly are pasted in.
* ‘Redeem’s option to select muliple boxes at once has been removed to relieve any confusion when inputting an amount to be redeemed: For example, if multiple boxes are selected at an amount of 3, and 1.5 is wanted to be redeemed - it was not clear from which redeem that amount of 1.5 was coming from. It is simpler now with individual redemptions only.


## Technology summary

In March we've focussed on magic numbers, 4h (hexidecimal) structure and assembly script-cbor.

Cach metadata we send starts with Rain magic numbers so we are compatible with everything build by/for Rain. This gives us access to a new paradigm of defi strategies and applications, and it also lets us have lots of asset classes.

Each hash we upload to ipfs nodes is indexed by the subgraph so ipfs nodes know what to pin and what not to pin.

### Magic numbers & hexidemical structures
Magic numbers facilitate portability allowing tooling to identify with high confidence that some data is intended to be interpreted in some way regardless of where it may be found in the wild and what anyone else on the planet might be doing with their data. We use specific magic number for different data.

For example when sending data to mint, we encode the data starting with a Rain magic number, to ensure data security. While posting the asset class we have our specific magic number for it as well, that specifies that the encoded data represents the asset class. Same for structure - that has its own magic number, and for hashes - with its own magic number.

### CBOR encoding
The data sent on-chain is cbor-encoded. And cbor libraries are used to encode/decode the data in subgraph and front-end. Cbor is json but more efficient and with binary support.

## What can you expect in April and May

* Website fixes
* Hosting moving more boxes to static IP / new ports
* Identify new countries for hosting resilience
* Ongoing Rain integration
* Website updates
* Minting website redevelopment begins

## More info

GILD LAB LIMITED
Company number 13684709
Address Unit 8, 28 Mill Street, Ottery St. Mary, England, EX11 1AD

Website https://gildlab.xyz/
Uptime https://upptime.gildlab.xyz/
Mint & Redeem https://sft.gildlab.xyz
Update https://hackmd.io/LkZPdu2RQuGiX3rw8Lk0GQ?view