@maol the 350k is not in my wallet anymore ... :( i have 350k sia coin before fork ...after fork i update my gui wallet to 1.3.7 then i transfer it to binance ...after 1 day i my binance account have receive it . then i was like wtf ......then i tried to trans 50 sia coin again to binance ...in less than 1 hour it went thru ...
STARTUP: Logging has started. Siad Version 1.3.7
2018/11/13 13:20:50.049214 encrypt.go:460: INFO: Unlocking wallet.
2018/11/13 13:30:39.248729 money.go:161: Submitted a siacoin transfer transaction set for value 350 KS with fees 22.5 mS IDs:
2018/11/13 13:30:39.248729 money.go:163: c715b751cf8de649300fd1edc0c36fe230efdb70d4444a249aa49b1997e60c39
2018/11/13 13:30:39.248729 money.go:163: 9e131cbd29205e80f7a311f47dcdfed9d9ac982a5478cdf5d8a361a31f60658c
2018/11/14 13:34:38.230405 persist.go:110: STARTUP: Logging has started. Siad Version 1.3.7
2018/11/14 13:37:54.366148 persist.go:110: STARTUP: Logging has started. Siad Version 1.3.7
2018/11/14 13:38:04.412195 encrypt.go:460: INFO: Unlocking wallet.
2018/11/14 20:19:48.556805 money.go:143: Attempt to send coins has failed - failed to fund transaction: wallet has coins spent in incomplete transactions - not enough remaining coins
2018/11/14 20:22:25.732182 money.go:161: Submitted a siacoin transfer transaction set for value 50 SC with fees 22.5 mS IDs:
2018/11/14 20:22:25.732182 money.go:163: db1d96724071e449b6f00e960e471266f2cc4bd7378edbd84d6324dfd5127bc8
2018/11/14 20:22:25.732182 money.go:163: a1a7e1bec2087584c6ea0b48bcf41224390d26e0761d065295b9d0f9abd9d250
2018/11/14 20:26:03.453262 persist.go:110: STARTUP: Logging has started. Siad Version 1.3.7
2018/11/14 22:58:56.116154 persist.go:110:
With "disaster recovery" I mean solving the problem of current single point of failure that only the uploader node has access to the data. At present if you lose your node by a system crash, crime or any other reason you lose your data uploaded to the network...
Backing up the node is not trivial as the node data files change continuously and you can lose your data if you lose the latest revision of the node data (particularly the "current" revision of storage contracts with hosts).
Can you elaborate on this a little more? Why do "node data files change continuously" - is this because the schema definition of the files is altered with each Sia client release?