[LCAC Conference] Lambda Storage Function Test Progress Conference

Lamb-CAC
7 min readNov 26, 2019

--

At 21:00 on November 11th, Beijing time, the LCAC- Lambda Core Governance Community sponsored by Node Pacific( LAMB Pacific) has held 30+ conferences with 5000+ participants. The Lambda Governance Committee and the project team jointly launched the preliminary selection of Lambda storage function access test technical miners team. Now that the storage function have been tested for one week, we invited all members of the Lambda Governance Committee and the miners technical team and organized the LCAC 41st conference in the LCAC community to share the progress of the Lambda storage function test.

Conference theme: Lambda storage function test progress conference

Conference Overview: The conference invited all members of the Lambda Governance Committee and the Lambda Technical Miners Mutual Aid Team to explain and share the Lambda storage function test progress and other issues.

Conference process:

— 1.Lambda storage function progress sharing

— 2. Question section

The following is an excerpt from the highlights of the conference:

01

Sharing of Lambda Technical Mutual Aid Team Miners:

1.Lambda Committee Miner Representative — Brother Rock

Hello everyone, I am brother rock, a real miner. Speaking of the test progress: the access test of the storage function has been carried out from yesterday to today, and it has to be done by the miners themselves. So, this time we the technical team didn’t do it. I have received professional training before, so I searched it in Baidu and installed the virtual machine to build all the miner nodes.

I found a problem : the threshold to access is a little high for other miners. Knowing something about the computer, I am technically better than most people, but for other miners, this is a problem as there are all command-lines. I have been operating according to the tutorial, the key of the tutorial is when create appears once, it has a check and view command, but there is no recording in the text tutorial. For the video tutorial, it is not very clear, which needs to be improved;

As to the technical support, a technical support team is very much needed. First, the video tutorial and the command line need to improve so that the miners can access without any difficulty; second, it’s needed to explain what’s are those command lines as the the newbies may not be able to solves those problems that I solved, they need to understand the operation rules of Lambda, as the actual access is not the same as the ordinary POC.

To sum up,we need more support from the technical team, more detailed video tutorials, more fool proof operation, and team incentive mechanism to make everyone more motivated to participate.

2. Technical Mutual Aid Team Member — Blue

First, the problems I encountered during the access process were similar to those of Brother Rock. I didn’t know if it was correct after accessing and executing the command line at the beginning, and didn’t know how to make corrections and check; however, the process became smooth after trials.

Second, there were some minor problems when uploading files through the external network. Now I am communicating with the technical team, whom need to check the code to identify the problem.

Third, the test network sees few people to participate in as the incentive mechanism is insufficient. It takes a lot of time to access the test, and there is no practical result after turning on the mining machine, which requires a subsidy plan, such as set the exchange ratio between testnet coins and mainet coins. Set an upper limit to prevent those people whom accessing too many times. If there is a subsidy for accessing, will more people come to access it? If there are more people come to access, there will be more problems found. If the people who access have better skill, they maybe pass by one try. If not, they may encounter various problems.

Fourth, I hope it can be encapsulated to simplify the operation.

3. Technical Mutual Aid Team Member — Jia Xuan

As to the access progress, it is similar to that of Brother Rock. I later thought of some suggestions after seeing that many miners want to test and have no internet IP, they use dynamic internet IP but can’t access; the network solutions is as follow

Consensus network, R1, R2, R3 here are nodes (with internet IP address)

Speaking of the storage side, a VPN can be established to connect miners’ access with the nodes.

Considering many miners currently do not have an internet IP address and they cannot access the test, we have the following designs.

Option 1: Think of referring to mpls vpn

When the user deposits the data, the mining machine information and the physical location information can be queried in the consensus network (in this aspect, it is estimated that there require parameters to compare each other to come out the optimal result and to match the storage. The basic information is: TTL hops, network quality, corresponding miner information, etc. I call it list information here)

=======

After the user matches the mining machine information, the user program can establish a VPN tunnel with the node, and then the node establishes a VPN tunnel with the miner. In this way, two tunnels get interconnected, to store the data.

(Why am I thinking of such, as at the network level, through the internet IP address of the node, a bridge can be hopped to enable miners to store and forward the data by relying on the node instead of internet IP.) But it also has disadvantages, that is, if the miner’s corresponding node is dropped, it will cause a disconnection.

=========================================================== =========

Solution 2: When User stores data, it searches the list information in the consensus network, matches the corresponding mining machine, and then transmits it through the upnp protocol, whom may have stability problems.

The mining machine can use UPNP to join the consensus network, but if the data is transmitted, it may be unstable.

UPnP supports zero configuration, “invisible network” and automatic detection; any device can automatically join a network, obtain an IP address, announce its own name, check its own functions according to the request and detect other devices and their functions. DHCP and DNS services are optional and will only be used when they exist on the network. The device can automatically leave the network without leaving any unwanted status information. Not evaluated)

The above are some of my thoughts, which I hope can help with underlying lambda technology!

Miners technical team members are wanted with generous incentives.

http://lambdacommunity.mikecrm.com/pJVCBRb

02

Question section

Q: About encapsulation ?

Committee member Brother Rock: At the primary stage, it may also need frequent changes, so the encapsulation does not make much sense; and only by by this technical means can we understand the technical principle of the entire Lambda, so the test may not be encapsulated.

Q: About the incentive mechanism?

Committee member Brother Rock: My feeling about the access these two days is that many people are very impatient in accessing. As a problem may take 1–2 hours to solve,they are not willing to spend the time in solving the problems if there is no incentive mechanism. So, this is critical on how to answer the questions and how many TBB miners help him to access for detailed quantification.

Committee member Zhang Xu A: I would like to share the current work progress with our community and technical team. The work is divided into two parts. Part one, about recruiting technical miners mutual aid team members we have recruited 10 skilled miners whom are encouraged to do the initial test access; Part two, at the same time, the committee and the Lambda team are in the process of drafting the entire test, technical support mutual aid team reward program which includes several items: the technical team must complete the access and test of the entire function, only when they complete the access will the technical mutual aid rewarded accordingly. The rewards are as follows: the rewards for the old to bringing in the new, which is calculated by the quantity; the rewards for technical team to answer technical questions and support community miners access, identify or repair major BUG according to the schedule, which is not capped; the rewards for detailed tutorial (video, text article, live training), and the rewards for the internal team (one-on-one tutoring given by the technical teams).

Technical team miner Blue asked: Now there is a time problem, the technical problems encountered while accessing are sent to the technical Wehcat group timely, while they can’t be answered all the time as Lambda technical team is too busy. So, it is recommended to arrange a fixed time to solve the problems.

Committee member Zhang Xu: This problem can be solved tomorrow. Our committee will communicate with the technical team to arrange a fixed time answering questions. At the same time, everyone can save our QA document in Shimo format released by our assistants in case there should be the same problems.

Committee member Dragon in the Mirror suggest: I think that high earning rate should be given at the early stage to mobilize the market. Plan how long it takes to break even if pledge 100P-200P given the fact that it takes 1–3 months to break even if pledge 50P and 3–4 months if pledge 50–100P at the early stage. By doing so, we can let the market truly realize the value. I will explain this further to the committee afterwards.

--

--