3. Losing coins by 2 wallets in the same network. ????...... :(

Losing coins by 2 wallets in the same network. ????...... :(

  • D

    I have run 2 different wallets on 2 different machines at home in the same network ( ip ).
    With sia 1.2.1 i got no problems to start up the wallets at the same time with the new version 1.2.2 it went a problem.

    1pc is accepting contracts the other not.

    Now with the new version my second pc has taken over the connection to the sia network. The second pc has no contracts.
    And my second pc has synced that wallet data with the network and haved destroyed the contracts. I think........ The same as you quit hosting.
    Now if i start my sia on my pc that must be the host to rent space with the contracts accepting. It connects to the network with his 1050 contracts and after a while 10, 15 minutes my host goes offline.

    UPDATE: I think i fixt this that my host was going offine ( its running fine again )

    1: i have created a static ip on my host pc and router en open the ports 9981 and 9982 ( Thanks reinisp )
    2: I deleted all firewall settings for sia who where there for sia and started sia up again windows firewall will ask you to give again sia permission.

    0
  • R

    @daan1980
    Do you use UPnP and let Sia manage ports on its own?
    Luckily I had the feeling it could go wrong, disabled UPnP in my router and set port forwarding manually to my real hosting node. My other nodes are not hosting so there is no need to forward ports.

    If you want to host from multiple nodes, you should configure the usual port forwarding (9981 and 9982) to your main node internal ip.
    For all other nodes you should configure port forwarding with different ports, for example,
    forward port 9992 to <node2 internal ip> port 9982,
    forward port 9993 to <node3 internal ip> port 9982
    ...
    Then announce the node2 with <your ip>:9992 and node2 with <your ip>:9993

    I think, it is sufficient that only one host (your main node) is reachable on port 9981.

    Important note:
    Don't operate more than one wallet created from one seed (in parallel)!
    Every working node should have own wallet (seed), especially if hosting or renting. You risk messing up your contracts if you create a "backup" or duplicate wallet from the seed.

    0
  • D

    First i let manage sia everything on its own. Now i have forward the ports in my router to the node.

    I just want to host from 1 node. The other node i used for backup my coins. That machine is most of the time offline.

    0
  • R

    @daan1980
    Your coins are safer if they are on a "nonhosting" wallet.
    I operate with 2 wallets (seeds)- one for storing coins, other for hosting.
    Just leave enough coins for collateral on the hosting node/wallet and transfer the excess coins to the new.

    0
  • D

    @reinisp Is there a non hosting wallet out there for sia? That would great for me.
    I also works with 2 wallets 1 for storing 1 for hosting. But i have a feeling that there a conflict as occured.
    Because the wallets hanging on the same ip.
    Do you now if it is posible to see how many collateral already is taken for the hosting or what you have lost?
    In my wallet i see a lot of withdraws but i am not sure if this is locked collateral or lost collateral.

    0
  • R

    @daan1980
    with "nonhosting" I meant just not hosting or renting. There is no special wallet.
    Just to clarify, you created 2 independent wallets (both wit init and not init-seed)? Or used the same seed for the second wallet?
    As I wrote, I have 2 independent wallets, on one external IP. The coins holding wallet does not need to be visible from outside. The only thing it needs is a connection to outside for syncing the consensus.
    And I still think, it helps to tell the "nonhosting" node that there is a nearby node for syncing by running
    siac gateway connect <internal (local network) ip from my main (hosting) node>:9981

    regarding collateral, run siac host -v on the hosting node and you'll see detailed status- collateral locked, collateral risked and collateral lost.
    For example I see:
    Locked Collateral: 10.4 KS
    Risked Collateral: 294.9 SC
    Lost Collateral: 0 H

    0
  • D

    This post is deleted!
    0
  • D

    @reinisp

    To clarify i have 2 independent wallets running in a local home network on 2 different pc,s / nodes on the same ip to the internet they have both there own seed and password.

    With siac gateway connect i don,t know exactly how it work i will look at that.
    I think you that you mean that it will sync the wallet faster from 1 pc to the other. :)

    Your answer if i have lost coins and how to check where great i didn,t lose any coins only locked. :) :) :)

    Thank you.

    I still got a little bad feeling with it to put the wallets online at the same time. Will it still be safe?... What wil happen in the new update?
    Or is it possible to force sia only to connect the wallet and not to put the host online?
    Maybe also handy?

    1 KS = 1000 SC
    Do you know how many 1mS is into SC? Is it less then 1 SC?

    0
  • R

    @daan1980
    It is safe to run more than one independent wallet on one external ip. You should just make sure your hosting node does not loose the ip forwarding in your router. I have set manually port forwarding to my hosting node. I even did not turn off UPnP, but as I see errors in the nonhosting nodes logfiles complaining about errors using UPnP, I know, the ports are forwarded to where they should.
    The "wallet node" has only one function- syncing the blockchain to see the balance and transfer coins if needed. I don't care if it is reachable or not (it says it is, but i'm sure that is not true).
    As a coin transfer between the two (wallet and hosting) nodes is really fast I assume everything is working as intended.

    0
Log in to reply