|
1209
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: ♦♦♦♦♦♦[ANN]♦♦MTR♦♦MasterTraderCoin♦♦10.4m♦♦TOSHIDESK LLC♦♦ETNA Partnership♦♦♦♦♦♦
|
on: October 19, 2016, 08:06:47 PM
|
There are several posts over the last few months where it was clearly articulated how he killed MTR by dumping the premine after he said he wouldnt. It is your own fault to believe him after that. I hope you get your money back but I wouldnt put money on that though. I didn't get scammed by his shitcoin, its something unrelated to this.. He offered me trading signals for a cost, check out the scam thread guys.  The chances of someone showing a certain characteristic in one place, showing the same characteristic elsewhere is high. |
|
|
|
|
1213
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][LOC]UPDATE V1.4.5 OUT!! LOCO|Quark|PoW/PoS|HiPos|Masternodes|Tor[LOC][ANN]
|
on: October 17, 2016, 04:45:18 AM
|
No there are actually people that are staking such small amounts:
2016/16/10 - 0.00068447 LOC which was an actual staking reward.
Such a transaction has approximately the same overhead than a single transaction of 10000 LOC. Now imaging adding 1000 of those small ones and having to pay 1.5+ LOC for the transaction fee. The tx fee will be more than the value of the tx. You will never be able to send the coins unless you add an input block to the mix of about 1.5 LOC so that you at least have a positive dust value for the tx.
txid please, that reward is pretty much the same that i have for POW blocks (0.00068448) here's example  do you realize that each tx value is 5.00068448 ? 02:24:56

Welcome to the Loco RPC console.
Use up and down arrows to navigate history, and Ctrl-L to clear screen.
Type help for an overview of available commands.
03:00:14

gettransaction 5d2d2ff92155cfb5009defe8d99435f4eab208a51bc77eafc941a40ffd584bc4
03:00:15

{
"txid" : "5d2d2ff92155cfb5009defe8d99435f4eab208a51bc77eafc941a40ffd584bc4",
"version" : 1,
"time" : 1476442800,
"locktime" : 0,
"vin" : [
{
"txid" : "892fc1e5bbb3653eb703390d49ca8be10b20c7e9f1596c8fa7e6b746e909e394",
"vout" : 0,
"scriptSig" : {
"asm" : "3045022100886050da7bfea591aa8c5f4adcbd182e4813a0d58691ef1fd9ef43f6fb0d667e02200646dd4d54eee325aa05ea6fa0e611cfb1c7db5cce01df8a34ce097b741d575b01 03c76ec2cb2011457a4dcc0478afd2f4f4d325891820c3b1331547aa70be14576d",
"hex" : "483045022100886050da7bfea591aa8c5f4adcbd182e4813a0d58691ef1fd9ef43f6fb0d667e02200646dd4d54eee325aa05ea6fa0e611cfb1c7db5cce01df8a34ce097b741d575b012103c76ec2cb2011457a4dcc0478afd2f4f4d325891820c3b1331547aa70be14576d"
},
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 0.00000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "",
"hex" : "",
"type" : "nonstandard"
}
},
{
"value" : 5.00068448,
"n" : 1,
"scriptPubKey" : {
"asm" : "03c76ec2cb2011457a4dcc0478afd2f4f4d325891820c3b1331547aa70be14576d OP_CHECKSIG",
"hex" : "2103c76ec2cb2011457a4dcc0478afd2f4f4d325891820c3b1331547aa70be14576dac",
"reqSigs" : 1,
"type" : "pubkey",
"addresses" : [
"5svExsoYQrwLdrYQdbH5szR6onxHBrzj7E"
]
}
},
{
"value" : 0.00068447,
"n" : 2,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 c6e899a49d0140be82e68648903e3a9b8c00b1f8 OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a914c6e899a49d0140be82e68648903e3a9b8c00b1f888ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"69ByFdTC9RoaKKe6vryoxx1pQ5FxAPRpdA"
]
}
}
],
"amount" : -0.00068447,
"fee" : 0.00136895,
"confirmations" : 4787,
"generated" : true,
"blockhash" : "e9db9ec20feb156aadc57ab08b1955ad39ebfd125526c1e0462d6d87fa8ab5fb",
"blockindex" : 1,
"blocktime" : 1476442800,
"txid" : "5d2d2ff92155cfb5009defe8d99435f4eab208a51bc77eafc941a40ffd584bc4",
"time" : 1476442800,
"timereceived" : 1476442800,
"details" : [
{
"account" : "",
"address" : "5svExsoYQrwLdrYQdbH5szR6onxHBrzj7E",
"category" : "generate",
"amount" : 0.00136895
}
]
}
idk if there are any masternodes running, maybe they have a bunch of tiny pieces coming from stakers Yes you are right. It is very difficult and confusing to analyse without a proper block explorer. Maybe there will be a new one after the next version of the wallet (if there is a next version) how exactly the reward structure works and what the split is between POW and staking. |
|
|
|
|
1215
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][LOC]UPDATE V1.4.5 OUT!! LOCO|Quark|PoW/PoS|HiPos|Masternodes|Tor[LOC][ANN]
|
on: October 16, 2016, 10:01:36 PM
|
Maybe just a point of interest. I notice that some people stake with small input blocks and the rewards are very small - in the region of 0.0006-0.006. This will cause those stakers to have very large transaction fees once they want to move or consolidate their coins. It is very easy for all those small rewards to cause a transaction fee more than the actual value of the combined transaction. Eg. 1000 blocks of such small amounts will have a smaller value than the transaction fee to process 1000 transactions due to the size of those transactions causing an insufficient funds scenario. To manually combine such small blocks will take ages as a few larger reward blocks will have to be selected together with a bunch of dust transactions in order for there to be enough value in the combination to cover the transaction fees.
I would recommend that stakers combine their coins once in a wile to have larger rewards and smaller transaction fees.
those small blocks are simply POW blocks (5 coins), nope, tx fee doesn't go thru the roof, i always manually combined them, but in fact all these things are boring No there are actually people that are staking such small amounts: 2016/16/10 - 0.00068447 LOC which was an actual staking reward. Such a transaction has approximately the same overhead than a single transaction of 10000 LOC. Now imaging adding 1000 of those small ones and having to pay 1.5+ LOC for the transaction fee. The tx fee will be more than the value of the tx. You will never be able to send the coins unless you add an input block to the mix of about 1.5 LOC so that you at least have a positive dust value for the tx. |
|
|
|
|
1216
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][LOC]UPDATE V1.4.5 OUT!! LOCO|Quark|PoW/PoS|HiPos|Masternodes|Tor[LOC][ANN]
|
on: October 16, 2016, 08:29:44 PM
|
|
Maybe just a point of interest. I notice that some people stake with small input blocks and the rewards are very small - in the region of 0.0006-0.006. This will cause those stakers to have very large transaction fees once they want to move or consolidate their coins. It is very easy for all those small rewards to cause a transaction fee more than the actual value of the combined transaction. Eg. 1000 blocks of such small amounts will have a smaller value than the transaction fee to process 1000 transactions due to the size of those transactions causing an insufficient funds scenario. To manually combine such small blocks will take ages as a few larger reward blocks will have to be selected together with a bunch of dust transactions in order for there to be enough value in the combination to cover the transaction fees.
In essence, staking such small input blocks is a waste of time. If it was a fixed reward it is another matter but this is percentage based rewards.
I would recommend that stakers combine their coins once in a wile to have larger rewards and smaller transaction fees.
|
|
|
|
|
1217
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][LOC]UPDATE V1.4.5 OUT!! LOCO|Quark|PoW/PoS|HiPos|Masternodes|Tor[LOC][ANN]
|
on: October 16, 2016, 08:08:48 PM
|
Wallet stopped at 381386 unit on October 8 th!!!???
nope, check forking: getblockhash 381386 ef517f583d0af2337a75b41f262ec1b0e39321d57dfffbe28d30f11c47005c3d healthy nodes right now:addnode=45.32.41.132 addnode=64.62.174.105 addnode=68.36.216.167 addnode=76.106.178.142 addnode=84.234.52.190 addnode=86.151.218.108 addnode=88.206.186.58 addnode=115.76.195.234 addnode=188.82.35.166 addnode=198.27.81.25 addnode=199.188.236.41 addnode=212.112.150.250 these report outdated versions, should be excluded:# addnode=5.189.189.51 # addnode=95.84.130.70 I can not check (getblockhash)- do not get a response wallet and wallet hangs. Maybe re-sync your wallet. Getblockhash 396523 c7b5e8e5c62c98188eebaeb9a29ac9f46ded91937a8f84f5e9f18b518e57ad39 |
|
|
|
|
1219
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: ♦♦♦♦♦♦[ANN]♦♦MTR♦♦MasterTraderCoin♦♦10.4m♦♦TOSHIDESK LLC♦♦ETNA Partnership♦♦♦♦♦♦
|
on: October 10, 2016, 07:01:18 PM
|
|
The dev killed the project when he dumped the premine into his own low buy orders. This is the only explanation why he would have kept it quiet and not told anyone of the imminent dump. It is similar to washing money. With the dump he moved a large portion of the premine "legitimately' to another account of his that no-one will know is his. Then he started a brief pump from about 100 sats to 2000+ (cant remember exactly) where he dumped the coins he sold to himself for about 7 BTC to unsuspecting buyers and then he disappeared again. He then invested the BTC into one of the big ICOs at the time, cant remember if it was LSK or one of those. I remember him bragging about the profit he made with the ICO.
It is time to realize that this project is dead. Luckily I got out a long time ago.
|
|
|
|
|
1220
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: WAVES. Ultimate crypto-tokens blockchain platform.
|
on: October 08, 2016, 11:21:39 AM
|
The full nodes is already finished?
it is a great news and we wait to see waves on polo soon.
No, still not released, if released the price is not this low. thats right if the full nodes completely been released we will expect mooning for the price, just give some little more hold and wait. If they were ready for full node release I am sure they would have released it by now. Hiring at this stage in the project just screams incompetency to me, like they have ran into multiple problems they cannot fix without help - Which is expected but why not advertise to hire months ago? Just my opinion, but I am not expecting full node release this month now. I think you are too hard on the dev team. There is nothing wrong with hiring more people. Afaik they have not said the reason for hiring additional developers is because that they have a problem they cannot solve. It could be a completely different reason like they want to put more work in parallel; they have reached full capacity and needs more capacity; they are working on future functionality not related to the launch of full nodes and prudently hiring for that now several months in advance of their plans to launch that functionality; or even replacing someone that have to move to another country. There could be many reasons. |
|
|
|
|
Show Posts
