ZenGround0

package main

import (
	"net/http"
	"net/url"
	"os"
	"fmt"
)

ZenGround0

package main

import (
	"io"
	"mime/multipart"
	"net/http"
	"net/url"
	"os"
	"fmt"
)

ZenGround0

go-filecoin file system access April 2019

Quick report on filesystem abstractions in go-filecoin

Strong abstractions

For the most part the repo provides strong abstractions for go-filecoin to use when interacting with fs objects.

Datastores

The paths from the repodir to the datastores are kept either in the config (in the case of the main datastore) or as global variables of the repo package in others in the case of the others. Datastores are opened in interal functions called from OpenFSRepo, and closed by Close. The go objects created are then made available through public methods.

ZenGround0

<!--
Please first see README for how to get help before filing a new bug report. 

If you have a *QUESTION* about Filecoin, please ask on our forum at https://discuss.filecoin.io/
-->

**Describe the bug**
<!-- A clear and concise description of what the bug is. -->

**To Reproduce**

ZenGround0

go-filecoin actor ls | jq 'select(.actorType == "MinerActor") | .address' | xargs -L1 go-filecoin miner power

ZenGround0

# Use this set of commands for tuning your logs to debug scenarios where your node can't sync the chain
# At a high level if your chain is getting stuck it is because one of 2 things is going wrong
# 1. Your node can't fetch the chain data
# 2. Your node can't correctly process the longest chain

# first quiet all logs to ERROR level
go-filecoin log level error

# listen to the details of chain related subsystems
# logs related to fetching 

ZenGround0

Intro

@sternhenri and @jzimmerman have proposed a strict timestamp validation rule for the filecoin network. The rule (1) is that all epochs uniquely determine a period in time fixed by the genesis timestamp. Blocks with timestamps that don't fall within the window specified by their height are marked as invalid by the protocol. This relies on a clock synchrony assumption.

Talking with @Kubuxu I learned that the lotus team is hesitant to adopt these strict timestamp rules for at least one major reason: recovery after chain halting. This document dives into the proposed timing validation rule and its impact on recovery from chain halting. It makes an argument for keeping these strict validation rules and explores some chain halting recovery options.

Timing model

During steady state operation (i.e. CHAIN_FOLLOW mode) a filecoin node mines off of the heaviest tipset it finds. Nodes mine with the appropriate number of null blocks to put their candidate block in the current epoch. If a node wins an

ZenGround0

var blockAtlasEntry = atlas.BuildEntry(Block{}).Transform().
	TransformMarshal(func(liveForm reflect.Value) (serialForm reflect.Value, err error) {
		return StructToTuple(liveForm)
	}, reflect.TypeOf([]interface{}{})).
	TransformUnmarshal(func(serialForm reflect.Value) (liveForm reflect.Value, err error) {
		return TupleToStruct(serialForm, reflect.TypeOf(Block{}))
	}, reflect.TypeOf(Block{})).
	Complete()

ZenGround0

// Protocol Constants
// Time Drand network starts at
DRAND_START_ROUND 
// Time of one DRAND Round
DRAND_ROUND_TIME
// Number of epochs in the past that a filecoin block should sample DRAND entries from
DRANDLookback = 2 // might change to 5 for availability reasons


func ValidateBlock(b BlockHeader) {

ZenGround0

go-filecoin uses static port 6000 by default but if you want to change to another port here's how.

1. After initializing the node navigate to configuration file config.json by default this will be at ~/.filecoin/config.json
2. Find the swarm section of the config:

"swarm": {                                                                                                                                           
                "address": "/ip4/0.0.0.0/tcp/6000"                                                                                                           
        }, 

3. edit the port number in the config