41K SC upload fee???



  • Who could tell me something about this transaction:
    d04d640c7ca788581bb37f5b66d50ecda26326ed068ea10fdece68e51ec25713
    I suspect what it is, but is it possible to be sure?

    @moorsc0de
    I think that is the end transaction for my renting period and my unspent allowance returned to my wallet.
    That would mean the unspent coins are returned. And that was in April. I think then the "current" version was 1.0.4 or 1.2.0.



  • Let's try out. I have at the moment the version 1.2.1 (UI) and 1.3.0 (hosting) running.
    type hostdb -v into the terminal and copy the info about 5 last hosts (the top5 scores).
    1.2.1:

      5:    ed25519:483bde42fef42cba862fd1ea5fbd878a5b29ff1ebe854c2f39ed07d07edf319a  84.219.196.111:9982                                     383530  39 SC                 9 SC                  1.000   111111
      4:    ed25519:280ea160a52b9658a17a61c039365b9138f3e09abb7ae4ed2ad4dc3222bd159f  sia.r3t.at:9982                                         392186  150 SC                1 SC                  1.000   111111
      3:    ed25519:f9ac0365b14a7e33137ed622aad27bf52ccd0bc1d238aa0794399630ba1beeb9  host.siadn.com:9982                                     432251  75 SC                 10 SC                 0.918   111111101111
      2:    ed25519:dbc24d575ccf99a307a6293f541ac0779516947bf9edba1fd21fe87ad6e018bd  zeusishosting.remotewebaccess.com:9982                  599213  70 SC                 35 SC                 0.991   111111111111
      1:    ed25519:3d57a0f24df26e1055924ab191b9838ebaa56a84d9662ed372b98c738d7e074c  99.248.51.247:9982                                      713349  50 SC                 25 SC                 0.998   11011111111
    

    1.3.0:

      5:    ed25519:f9ac0365b14a7e33137ed622aad27bf52ccd0bc1d238aa0794399630ba1beeb9  host.siadn.com:9982                                4.95726e+08  75 SC                 10 SC                 0.984   111111110001111111111111111111
      4:    ed25519:ed5578ad8a0f5bdaf24c5568b6f140ea44e556e10ed6db600d2890912e6b11ea  ru-moscow.sia.ix.gs:9982                           3.39415e+09  10 SC                 1 SC                  0.985   111111111111111111111111111111
      3:    ed25519:dbc24d575ccf99a307a6293f541ac0779516947bf9edba1fd21fe87ad6e018bd  zeusishosting.remotewebaccess.com:9982             3.94594e+09  70 SC                 35 SC                 0.996   111111111111111111111111111111
      2:    ed25519:8d33cb63f933a036300a05d696c8c683bb9cd4b6a92f5b17975422709cfc79d5  eu-central.sia.ix.gs:9982                          6.41817e+11  10 SC                 1 pS                  1.000   111111111111111111111111111111
      1:    ed25519:00252176ef25cce5bc4981d1e5522219cac9e41cfe6051aaf9369b32acc50d99  sia.eusap.com:9982                                 2.36875e+12  20 SC                 1 pS                  0.990   111001111111111111111111111111
    
    

    The first number following the address is the score for host selection when setting allowance...
    Which hosts are the topscorers in your hostdb?

    edit, from siahub:

    0.01282459 / #5	176.9.143.138:9982	5.5 TB	91.0 GB	2%	50 SC
    0.02207321 / #4	ru-moscow.sia.ix.gs:9982	990.0 GB	0 B	0%	10 SC	View
    0.02387527 / #3	zeusishosting.remotewebaccess.com:9982	5.4 TB	864.2 GB	16%	70 SC	View
    4.19997150 / #2	eu-central.sia.ix.gs:9982	10.0 TB	0 B	0%	10 SC	View
    15.50082455 / #1	sia.eusap.com:9982	6.3 TB	107.1 GB	2%	20 SC	View
    

    host.siadn.com:9982 is #8 in siahub
    siahubs #5 is #262 on my host. I would say my host thinks it has problems with uptime.



  • @reinisp said in 41K SC upload fee???:

    d04d640c7ca788581bb37f5b66d50ecda26326ed068ea10fdece68e51ec25713

    u need to create seperate posts because your mixing in too much stuff... I cant even follow what your asking.

    I mean we are here to help=- but spending all day deciphering Sia .. thats what Dev gets paid to do.

    Unofficial User / Tester / Analyst of Sia ( w/Renter and Host experience)

    0


  • @reinisp said in 41K SC upload fee???:

    I am not sure what are you trying to do? Host database and host ratings in it are different for ALL clients.

    And these differences occur not only because of the different client versions used (in which the rating calculation formulas may differ), but also on how long a particular copy of the client was online and how many times it was restarted before the database snapshot was taken.
    Because it depends on how many hosts the client managed to interrogate (by default, only 200 are checked, and now there are more than 600 online hosts in network, my own host discover only 510 from >600 total after few days of work and ~5 restarts) and how many statics on the hosts up-time it managed to accumulate.
    Because of this factors, each client has its own rating table, significantly differ from any other table from any other client. For example, here is my table with top-10 hosts from a client(v. 1.2.2) worked for about 3 days on the network

      10:   ed25519:3d57a0f24df26e1055924ab191b9838ebaa56a84d9662ed372b98c738d7e074c  99.248.51.247:9982                                 1.65922e+06  50 SC                 25 SC                 1.000   111111111111111111111111111111
      9:    ed25519:f9ac0365b14a7e33137ed622aad27bf52ccd0bc1d238aa0794399630ba1beeb9  host.siadn.com:9982                                1.79133e+06  75 SC                 10 SC                 0.967   111111110011111111111111111111
      8:    ed25519:997480e6074e8580accc097ec23d6116a5f35657008f70133db20b2f23f465a3  [2001:41d0:a:1785::1]:9982                         3.10865e+06  10 SC                 1 SC                  0.974   111111111111111111111110111111
      7:    ed25519:f8de8a0b81783035692c004975825f26e23b9a4825c55269d0bdadf34008b94d  176.12.25.174:9982                                  3.3816e+06  1000 mS               1 SC                  1.000   111111111111111111111111111111
      6:    ed25519:3fb09f23482814e2eb7978ead26ea09835f276fde5a1a5515662478e26d5a487  pingpongen5.ddns.net:9982                          4.03854e+06  75 SC                 15 SC                 0.927   111111100001111111111111111111
      5:    ed25519:d9d01b722fb0ea50de9aac3950fc43308243ac2eb840d794f32dfbe7d13f0ea7  176.9.143.138:9982                                 7.82771e+06  50 SC                 1 SC                  1.000   111111111111111111111111111111
      4:    ed25519:ed5578ad8a0f5bdaf24c5568b6f140ea44e556e10ed6db600d2890912e6b11ea  ru-moscow.sia.ix.gs:9982                           1.24774e+07  10 SC                 1 SC                  1.000   111111111111111111111111111111
      3:    ed25519:dbc24d575ccf99a307a6293f541ac0779516947bf9edba1fd21fe87ad6e018bd  zeusishosting.remotewebaccess.com:9982             1.45058e+07  70 SC                 35 SC                 1.000   111111111111111111111111111111
      2:    ed25519:8d33cb63f933a036300a05d696c8c683bb9cd4b6a92f5b17975422709cfc79d5  eu-central.sia.ix.gs:9982                          2.35941e+09  10 SC                 1 pS                  1.000   111111111111111111111111111111
      1:    ed25519:00252176ef25cce5bc4981d1e5522219cac9e41cfe6051aaf9369b32acc50d99  sia.eusap.com:9982                                 7.72038e+09  20 SC                 1 pS                  0.968   100011111111111111111111111111
    

    P.S.
    I agree with @moorsc0de. If you want to plunge into the details of how ratings and choosing host work, better start a new separate topic and ask the moderators to move a few recent post(including this one) to it.



  • @moorsc0de said in 41K SC upload fee???:

    and on top you dont even know how many contracts came in each day because the v1.2.2 was incrementally increasing contract count every time the UI was rebooted. So the actual ledger of collateral is a figure derived from what? There is no file to actually go back to and make a coin by coin or contract by contract audit to know if this is working properly. Your just looking at numbers on a screen.

    Just found what this bug (increasing contract count at every restart) not in UI (GUI) part. It is in the core code (siad) itself. I use siad without GUI and have seen the same - after each daemon restart contract counter increases.
    I even figured out pattern - it simply add actual number of contacts to previous value.
    So if you have 15 contracts for example counter will be doing +15 at each client restart.
    If you check counter before and after restart and do new-old = actual number of active contracts on host.
    Of course this is another bug and needs to be fixed - just workaround for now.

    Contract collateral stat on other hand calculated correctly by my observation. It is not depended on contract counter and calculation based on blockchain transactions.



  • @Mad_Max
    Yes this has been ongoing- now whether or not you have pinpointed WHERE the issue is coming from is a totally diff ball of wax..
    Its almost pointless because until the dev team fixesit the issue will continue.... but this issue is known by them- why it has not been fixed or maybe it will be is another question too.

    But let me ask this question.. Sia cant count the number of contracts properly.. but they can provide encrypted 3x redundancy across hundreds of nodes? (no answer required)
    Confidence very low...very

    Unofficial User / Tester / Analyst of Sia ( w/Renter and Host experience)

    0


  • @moorsc0de , @Mad_Max
    I see, I could be wrong with my assumptions.
    In that case the fundamental problem would be the renters node not updating the hostdb regularly and in short enough periods.

    My post regarding my particular transaction was meant as an example that unspent allocation IS actually coming back to the renter not only "per documentation".

    Let's hope today is that Friday (and not again the next one) the new updated UI is released and look if these issues persist.



  • @reinisp "HOPE"??? lol

    I think people are so desperate for Sia to work is they have been sold a bill of goods that is not Truthful. So "HOPE" is the order of the day now... but in technology- there is no hope. You either code or you do not.

    Unofficial User / Tester / Analyst of Sia ( w/Renter and Host experience)

    0


  • @reinisp In theory it should be ok - current renter module scan 200 hosts immediately after start (and do additional 200 scans each few hours of online work) . And it only need select 50 best hosts to make initial batch of contacts.
    Even considering that 200 hosts are randomly selected and that the user can start the process of contracts formation(by setting allowance) immediately after the launch. Among the randomly selected 200 hosts from current network, will be enough good hosts to drop all rogue hosts at least below the 100th position and never choose them again after very first scan. Probably the hosting prices will be far from most optimal point in this case (because renter did not discover best offers at this stage yet), but to check 200 hosts should be enough to does not choose the fraudulent hosts with absurdly high tariffs.
    But for some reason it still happens sometimes. Apparently there are more errors in renter logic/code.

    Let's hope today is that Friday (and not again the next one) the new updated UI is released and look if these issues persist.

    Nope. Not this Friday again. And I think that it will not be ready next Friday either.

    I think this is a patch to the renter logic devs mentioned to you: https://github.com/NebulousLabs/Sia/commit/59105d8a4a5a845f22977072ee2b4f3945d37bc2
    As you can see source code of patch was published only 9 days ago. It is not verified by other programmers and did not tested yet. So i think it will takes few weeks more before updated renter logic will be officially published and ready for use by ordinary users of sia.

    My post regarding my particular transaction was meant as an example that unspent allocation IS actually coming back to the renter not only "per documentation".

    And you got all this 52 690 coins back (minus only 10 SC from original 52 700 SC)?

    Actually this does not look like a return of locked collateral. But more like ordinary transaction. But i am not sure - i can not check detail because official block explorer is buggy too. If i try to check parent transaction or history it throw errors - "Hash not Found in Database" and "Block Not Found Database"



  • Reading a lot on here that is telling me to sell my few siacoins



  • @jhip626
    It's your decision.
    I bought a bunch of SC when the price was 110 satoshi (september 2016) and sold when the price fell to 40 satoshi (january this year).
    And I am sure the massive price rise 2-3 months ago has nothing to do with development of decentralised storage solution named Sia.
    I just know what was the price of a SC 6 months ago. And there has been less development as expected, partially because of the massive price rise, "user" (trader/hodler) influx and resulting problems with scalability at the exchange wallets.
    That rise was pure speculation, now the price nears slowly to the real value of present.

    So, you could exchange your holdings of SC into SJCX or MAID to be at least related to storage solutions.



  • @Mad_Max said in 41K SC upload fee???:

    And you got all this 52 690 coins back (minus only 10 SC from original 52 700 SC)?

    Actually this does not look like a return of locked collateral. But more like ordinary transaction. But i am not sure - i can not check detail because official block explorer is buggy too. If i try to check parent transaction or history it throw errors - "Hash not Found in Database" and "Block Not Found Database"

    I'm not sure if it is. The return of unspent is the only explanation of that transaction. Because both- sender and receiver addresses are my addresses, belonging to one wallet. And I am sure I did not transfer coins to myself within one wallet.
    On january the value of 50KS was so low I decided to abandon Sia, deleted all my test files from the renter and did not even open my wallet for more than 2 months. At that time 50KS was the minimum to start hosting, and seemed not to much for allowance... I really don't remember what did I set as allowance.



  • @reinisp There is at least one another situation when your coins are sent to your own address within one wallet without your actions.
    Before client lock in coins in file contract it prepare coin output with exact coins amount.
    For example

    1. You are a renter and going to sign contract with host which need 100 SC to be locked in it.
    2. But your wallet has only one big input (incoming transaction). Let's say = 50 000 SC.
    3. In such case your wallet takes/generate 2 new addresses and sends 100 SC to 1st and 49900 SC to 2nd address. First 100 SC used to sign contract and 49900 remain in wallet for future use.

    Wallet does such split/change transactions within one wallet automatically at every signed contract.
    I think this is happening at both sides (host and renter). Although I've checked it from the side of the host only for now.

    In GUI such transaction displayed as 0 (zero) coins transaction because net sum (input - output) = 0 as all addresses involved belongs to same wallet. But in blockchain you will see moving of large amounts of coins.



  • @Mad_Max The 0 transaction is the Sia Fund transaction that goes to them... your overthinking that.

    Unofficial User / Tester / Analyst of Sia ( w/Renter and Host experience)

    0


  • @moorsc0de What? What they have to do with this?
    SeaFund fees paid only by renters, not by hosts. And AFAIK there are not separate txs but fees included in file contract unlock process. Just amount of coins going out from contract after unlock fewer compared to amount of coins going in. All the difference is claimed by sea-fund owners later.
    Similar to bitcoin transaction fees, where is not any tx from users to miners, but miners claim difference between sum of all inputs and all outputs in all transaction in a block. But in Sia we just have 2 types of fees. One still goes to miners (tx fees) and other to siafund owners (contract fees)

    And as for these "zero" transactions - you can choose a hash of one of these and check it in the blockchain explorer to make sure that all the addresses involved in it are in your wallet. (to list all your addresses "wallet addresses" command in terminal or "siac wallet addresses" in command line)

    Wallet constantly creates them. I manually generated only 2 addresses, and now my wallet contains several dozen already, through which these automatic exchange/split transactions passed. Number equals to my host contact count (real count, bot buggy counter in current client)



  • @Mad_Max I deleted the file right after seeing the 41k go walkies, I emptied my wallet right away after and don't intend to restart the client for a long time, will that be enough not to renew?

    @moorsc0de BTW I was/am running 1.2.2 but the original contract would have been made under 1.2.1 but the xfer happened with latest version.



  • @desgrippes Sounds buggy

    Unofficial User / Tester / Analyst of Sia ( w/Renter and Host experience)

    0


  • @Mad_Max Do you have a source for indicating ONLY renters pay for Sia Fund 3.9% fee?

    Its my knowledge - Every transaction - in the UI (except deposits to the UI/wallet have a 0 dust fee transaction. These 0 SC transactions are the 3.9% of the amount being transacted that goes to Sia Fund.
    When you go to the Sia Explorer it will show you the dust transaction which is this 3.9% which is usually very minimal, but it comes out of every transaction- most users do not even know it.
    The wallet always creates multiple addresses... the wordis all of them will work.. but concerning specifically the 0 SC seen.. that is a 3.9% fee. This could get divided to the miners (not sure), but
    there would be no reason to show mining fees in a wallet (and would be a first I have ever seen of any wallet). These 0 SC are also going to different wallt addresses seen in the UI and in Sia Explorer.

    My post from reddit 20 day ago and was never contested there:
    Sia is a product of Nebulous Incorporated. Nebulous is a for-profit company, and Sia is intended to be- come a primary source of income for the company. Nebulous intends to generate revenue from Sia in a manner proportional to the value added by Sia, as determined by the value of the contracts set up between clients and hosts. This is accomplished by imposing a fee on all contracts. When a contract is created, 3.9% of the contract fund is removed and distributed to the holders of siafunds . Nebulous Inc. will initially hold approx. 88% of the siafunds, and rest 12% is held by the early crowd-fund backers.

    Source: http://www.cryptocoinscorner.com/2017/06/crypto-currency-siacoin-sia.html

    Unofficial User / Tester / Analyst of Sia ( w/Renter and Host experience)

    0


  • @desgrippes said in 41K SC upload fee???:

    @Mad_Max I deleted the file right after seeing the 41k go walkies, I emptied my wallet right away after and don't intend to restart the client for a long time, will that be enough not to renew?

    Yes, this should be enough.
    In order to renew contract client needs to use your private keys. So if you do not start client until old contracts expire OR you start client but wallet remain locked all the time - client will not be able to renew contracts. And without renew fund locked in old contracts should return to your wallet after contracts duration ends (12 week from contract signing by default).

    Resetting renter allowance to zero should work too. But i am not sure this works properly in current client... So i advice to clear allowance only after contracts expire and coins return back to wallet but before you unlock wallet and send coins away. Don't forget to do this before unlock wallet or client could start making brand new contracts using returned coins.



  • @moorsc0de

    Yes, 3.9% fee apply to all file contracts. But not to regular transactions.
    And these fees paid by renter only. Renter pay fees for both sides - own spending plus host collateral.
    This mentioned in the Hosting Handbook

    How Collateral Affects Score
    Collateral actually has two effects. The first is that it improves your score because renters like to see collateral. But the second is that it reduces your score, because renters have to pay a siafund fee on the collateral.

    And i also saw this on practice while browsing examples of renter contracts. Here link to table with examples of renter contracts. https://docs.google.com/spreadsheets/d/1KD1tdxc78okXeu4c2z4vWnVr1p9aaaqCXlwfaMmNZ9M/
    Pick 1st - 2d3ac4c5c88211a1a4f51f326643bd76651121e0722cc409db582bd9a97e5eb4
    Check block explorer: https://explorer.siahub.info/hash/2d3ac4c5c88211a1a4f51f326643bd76651121e0722cc409db582bd9a97e5eb4

    There is 1341.29 SC locked in this contract (Payout: 1,341.29 SC).
    But only 1288.98 SC will be paid to renter and host after contract finished (Total SC Outputs: 1,288.98 SC )
    Difference between this two values is a seafund fee: 1341.29*(1-3.9%) = 1288.97969 SC
    But this fee not visible in a wallet. You can see it only in the blockchain. And there is not any fees transaction - just sum(outputs) < sum(inputs)

    And now let's check who pay this fees:
    Renter sent 343.34 SC to form this contract (https://explorer.siahub.info/hash/49d0b260001dbb0f446b9953107bba612e6750365116a4eb13e2e7896cab4804)
    And 59.36 SC already marked as spend in client contract table.
    Host sent only 1000 SC as collateral to contract: https://explorer.siahub.info/hash/b348dafcb931b4d916706d3116c8e3277d752cedf3a8643b846684ce925652cf
    And 1005 SC is already prepared to return to host - all collateral + contract creation fee (from renter to host) 1000+5=1005 SC.
    If renter will never use this contract - host will get 1005 SC back, and renter will get 283.98 SC back.
    If renter will use it - host's portion will increase and renter portion will decrease.
    So all seafund fees is on a renter side.

    As for 0 SC transaction in a wallet - i am sure it is not a fees, but some sort of change operations. I have checked few such transaction in properly working block explorer (https://explorer.siahub.info/ - it is working much better compared to official one!). Here one example of "zero transaction" from one of my wallets: https://explorer.siahub.info/hash/fcdd92f88c783f9ed902d2fa9cd7bea60b37ea15d64a91fcb37798630eb28c26

    You can see it actually not a zero at all. 36.65 SC goes from one address (input) to two other addresses in 5.08+31.57 SC proportions. Only one reason why client shows this tx as zero because all 3 addresses are my own and total wallet balance change as result of such transaction = 0. Eg just sending coins to myself. If you send some bitcoins to own address (from the same wallet) bitcoin client will show such transaction as zero too.


Log in to reply