Topic: [ANN][LimecoinX Rebrand to BitSend] - page 43. (Read 110702 times)
it was 40 minutes ago, transaction should go to the next block and I have not limx in local wallet yet
I sent LIMx of bittrex to my wallet
http://blockexperts.com/limx/height/00a06b9e7a2bf08374777dc4bdaf63e37ea117b1f8a3d3f59fcd97c1c885e667
It's been 30min, and LIMx not reached the local wallet
What does "LimeCoinX block #S" in blockexplorer?
http://blockexperts.com/limx/height/00a06b9e7a2bf08374777dc4bdaf63e37ea117b1f8a3d3f59fcd97c1c885e667
It's been 30min, and LIMx not reached the local wallet
What does "LimeCoinX block #S" in blockexplorer?
the blockexplorer isn´t uptodate at the moment, i´ll try a small withdraw of the big bunch i bought yesterday on bittrex
This was a Orphan from "Bigminer".
I understand, but why LIMx did not reach the local wallet
Address: i3sHYLJBnw7qyUzuK64sk12ZpH4ib9a8jG
TxId: 00a06b9e7a2bf08374777dc4bdaf63e37ea117b1f8a3d3f59fcd97c1c885e667
edit : bittrex a bad chain, fork ?
Address: i3sHYLJBnw7qyUzuK64sk12ZpH4ib9a8jG
TxId: 00a06b9e7a2bf08374777dc4bdaf63e37ea117b1f8a3d3f59fcd97c1c885e667
edit : bittrex a bad chain, fork ?
I sent LIMx of bittrex to my wallet
http://blockexperts.com/limx/height/00a06b9e7a2bf08374777dc4bdaf63e37ea117b1f8a3d3f59fcd97c1c885e667
It's been 30min, and LIMx not reached the local wallet
What does "LimeCoinX block #S" in blockexplorer?
http://blockexperts.com/limx/height/00a06b9e7a2bf08374777dc4bdaf63e37ea117b1f8a3d3f59fcd97c1c885e667
It's been 30min, and LIMx not reached the local wallet
What does "LimeCoinX block #S" in blockexplorer?
the blockexplorer isn´t uptodate at the moment, i´ll try a small withdraw of the big bunch i bought yesterday on bittrex
I sent LIMx of bittrex to my wallet
http://blockexperts.com/limx/height/00a06b9e7a2bf08374777dc4bdaf63e37ea117b1f8a3d3f59fcd97c1c885e667
It's been 30min, and LIMx not reached the local wallet
What does "LimeCoinX block #S" in blockexplorer?
http://blockexperts.com/limx/height/00a06b9e7a2bf08374777dc4bdaf63e37ea117b1f8a3d3f59fcd97c1c885e667
It's been 30min, and LIMx not reached the local wallet
What does "LimeCoinX block #S" in blockexplorer?
Message from Aika!!
Updated to:
Limecoinx version v0.11.2.27-659eb12-beta (2015-05-13 00:38:09 +0200)
others pool ?
my wallet not sync - stunked at 90276. anyone else have problems with synchronization ?
No is correct...bchain/ Aika have old protocol.
https://www.cryptopia.co.nz/BlockExplorer
my wallet not sync - stunked at 90276. anyone else have problems with synchronization ?
Thnx for the PM dev Really usefull for lazy people like me who dont check threads everyday 
Wallet and masternode updated
Really usefull for lazy people like me who dont check threads everyday Wallet and masternode updated
addnode=96.2.40.126:8886
addnode=5.56.209.255:8886
Please UPDATE your Masternode 11.2.27
addnode=5.56.209.255:8886
Please UPDATE your Masternode 11.2.27
Hi Mates,
We changed 40/10 mining reward to all, solo miners are not longer at a disadvantage.
The Version 11.2.27 is available on github ! Clients following in a few minutes.
- new Hardnodes added
- Reward for all 40/10 - solominer and pools 40 LIMX & 10 LIMX for Masternodes
- halving MinTxFee
- halving MinRelayTxFee
- DGW/KGW fix
- DS timeout is now higher
- MASTERNODE_MIN_DSEE_SECONDS and MASTERNODE_PING_SECONDS now higher
- with command "masternodelist pose" can you see bad masternodes (5 = max)
The shutdown of bad master nodes is currently still inactive.
- Protocol version pump to 70076
https://github.com/LIMX-SUPPORT/LimecoinX
QT Linux in work
Regards Christian
We changed 40/10 mining reward to all, solo miners are not longer at a disadvantage.
The Version 11.2.27 is available on github ! Clients following in a few minutes.
- new Hardnodes added
- Reward for all 40/10 - solominer and pools 40 LIMX & 10 LIMX for Masternodes
- halving MinTxFee
- halving MinRelayTxFee
- DGW/KGW fix
- DS timeout is now higher
- MASTERNODE_MIN_DSEE_SECONDS and MASTERNODE_PING_SECONDS now higher
- with command "masternodelist pose" can you see bad masternodes (5 = max)
The shutdown of bad master nodes is currently still inactive.
- Protocol version pump to 70076
https://github.com/LIMX-SUPPORT/LimecoinX
QT Linux in work
Regards Christian
LIMX support makes contact. Thanks for the helpful hint.
Regards
Regards
Hi Mates,
The big miner wants to many LIMX. That makes me happy. He has a very high performance hash.
He also does not pay to the master node.
One solution would be to enable the spork. Accurate documentation I have not found it.
Eduffi: https://dashtalk.org/threads/v0-11-0-darkcoin-core-release.3601/page-25
Regards Christian
...I'll stay tuned
The big miner wants to many LIMX. That makes me happy. He has a very high performance hash.
He also does not pay to the master node.
One solution would be to enable the spork. Accurate documentation I have not found it.
Code:
09:44:59

spork SPORK_1_MASTERNODE_PAYMENTS_ENFORCEMENT 1431330800
09:44:59

failure
Code:
getblocktemplate
..................
"payee" : "iN3ZDLbwds8Cj2p2Br1PG3VWTD4kxLrBrZ",
"payee_amount" : 2500020000,
"masternode_payments" : true,
"enforce_masternode_payments" : true
}
Eduffi: https://dashtalk.org/threads/v0-11-0-darkcoin-core-release.3601/page-25
Code:
enforce_masternode_payments is always true now, the spork has been removed.
However, the network is in "fallback" mode, where miners pick who to pay and nothing is enforced.
I'll turn back on the reference node when everything is stable and everyone is up-to-date.
It's a bit confusing and there's some undocumented features of the code for situations like this.
Regards Christian
...I'll stay tuned
If I understand correct, that big miner is the Yaamp multi pool. Look at this: http://yaamp.com/site/block?id=1009. At least they are one of those miners who do not pay to masternodes. (looks like we have multiple such miners now...). I do not think they do that intentionally; it is a relatively old and legit pool. You can contact them to find the details...
Hi Mates,
The big miner wants to many LIMX. That makes me happy. He has a very high performance hash.
He also does not pay to the master node.
One solution would be to enable the spork. Accurate documentation I have not found it.
Eduffi: https://dashtalk.org/threads/v0-11-0-darkcoin-core-release.3601/page-25
Regards Christian
...I'll stay tuned
The big miner wants to many LIMX. That makes me happy. He has a very high performance hash.
He also does not pay to the master node.
One solution would be to enable the spork. Accurate documentation I have not found it.
Code:
09:44:59

spork SPORK_1_MASTERNODE_PAYMENTS_ENFORCEMENT 1431330800
09:44:59

failure
Code:
getblocktemplate
..................
"payee" : "iN3ZDLbwds8Cj2p2Br1PG3VWTD4kxLrBrZ",
"payee_amount" : 2500020000,
"masternode_payments" : true,
"enforce_masternode_payments" : true
}
Eduffi: https://dashtalk.org/threads/v0-11-0-darkcoin-core-release.3601/page-25
Code:
enforce_masternode_payments is always true now, the spork has been removed.
However, the network is in "fallback" mode, where miners pick who to pay and nothing is enforced.
I'll turn back on the reference node when everything is stable and everyone is up-to-date.
It's a bit confusing and there's some undocumented features of the code for situations like this.
Regards Christian
...I'll stay tuned
We have a miner in the network does not pay to the master nodes.
https://bchain.info/LIMX/addr/iF2C8J4DNCfzi3Lf53HrPesT5TfukXXMA7
Regard Christian
https://bchain.info/LIMX/addr/iF2C8J4DNCfzi3Lf53HrPesT5TfukXXMA7
Regard Christian
How is it possible?
The linux guide for masternodes needs adjustments. The guide recommends Ubuntu 14.04 which is not ideal, since the pre-compiled binary as well as the source depends on libdb4.8. Libdb4.8 was upgraded to libdb5.1 in 14.04 and onwards and therefore there are no 4.8 dblibs to apt-get and the pre-compiled binary fails. The instructions must be changed to recommend 12.04. If however 14.04 remains recommended, then the instructions must be upgraded to either give workarounds to get 4.8 compiled and installed or to recompile the source on the VPS with 5.1 using the the incompatible db switch or change the source to use 5.1.
Do you have a Githubaccount? We are grateful for any assistance.
Jump to: