Total paid: 1.103019BTC
Total deposited: 1.090411BTC How's that possible? You paid out more than people deposited. Progress to next payout 0.0002BTC / 0.0038BTC Are you sure? I see different values on blockchain: because you use change addresses on spent outputs. I wouldn't call that transparent enough. Random function you're using (probably mt_rand) is total crap!! Users might get 110% or 150% with no probability differences, and same for timer (talked about it below). You copied 7streak' old system, which we have ascertained it doesn't work. I suggest you to read their entire chat on website  At last, you also copied their texts: "Amount Wagered", "Possible Winning" etc. Copycats. |
|
|
|
Of course you are mad about this topic, since by looking at your trust, you are on of these ponzi owners Exactly. It's fun to see which users don't like this post:  I was one of the developers of the old and premier PONZI TGB, so what? It naturally collapsed after 250 BTC input. We didn't scam any of the users, don't talk bullshits please. |
|
|
|
In Bitcoin.org, it is "skip" and I think "skip" suit in this command better. "[skip=x]", where x is number of the most "recent transactions" which "should not" be shown.* When you ran first command, seven transactions where shown. When you ran second command, recent 6 transactions weren't shown as "skip value was 6". Hope this solve your doubt. If you want to study more, I suggest to you to look Bitcoin.org [1]. I find it quite useful and easy to understand than Bitcoin wiki. listtransactions API: https://bitcoin.org/en/developer-reference#listtransactions* Rephrased sentence from Bitcoin.org. [1] https://bitcoin.org/en/developer-referenceWell explained, thank you. Since I'm going to work with about 2.000 transactions a month, should I keep using listtransactions command? |
|
|
|
Hello fellows! I'm actually running bitcoind server to receive and send transaction through my own software. Transaction size of my spends are always near to 100kb/500kb, so how do I set a minimum/pseudo-fixed transaction fee in my bitcoin.conf/software? If you haven't figured out yet what I mean, I would always pay 0.0001 BTC for each spend cause they never exceed 1.000kb. Hoping in a fast reply  You can't, the reference implementation wallet always pays some-amount-per-1000-bytes-of-the-transaction. The rules for the 0.10 release are: + By default, you always pay a fee (this is different from previous releases that would send transactions without a fee if they had high enough priority) (run with -sendfreetransactions=1 to get the old behavior of sending high-priority transactions without a fee) + By default, the fee-per-kilobyte is estimated based on recent transaction confirmation history. To get close to what you want (pay a fixed fee per transaction), run with -paytxfee=0.whatever : that tells the wallet code to pay 0.whatever BTC per 1000 bytes. Most transactions are about 500 bytes big. See here: http://core2.bitcoincore.org/smartfee/fee_graph.html ... for how high to make -paytxfee=0.whatever based on how long you're willing to wait for the first confirmation (that page graphs estimates from the latest&greatest fee estimation code from Alex Morcos that will hopefully be in the 0.11 Bitcoin Core release). I'm now having full control of fees through: - getbalance
- listunspent
- createrawtransactions
- signrawtransaction
- sendrawtransaction
Previous method was working fine but when change addresses (inputs) were too much I started spending more than 0.0001 BTC, complete chaos  However now's everything ok with new functions So you are not using change addresses now? Or only a few specific change addresses? I'm no expert but I wonder if that would be totally safe? I guess maybe if anonymity isn't the goal... My software needs to be as transparent as possible, that's the goal yes. Change address is always the same spent input Testnet example: https://www.blocktrail.com/tBTC/address/mzkKmWG9Sj4duFDzHQMvwEvt1S8f3K56sm |
|
|
|
Hey there, I'm back  This time I'm having troubles with listtransactions function because "from" parameter is not properly working! I'm actually working on this address: https://www.blocktrail.com/tBTC/address/mzkKmWG9Sj4duFDzHQMvwEvt1S8f3K56smFirst command: listtransactions bitcoin 100 0 [
{
"account" : "bitcoin",
"address" : "mzkKmWG9Sj4duFDzHQMvwEvt1S8f3K56sm",
"category" : "receive",
"amount" : 0.00100000,
"vout" : 0,
"confirmations" : 6,
"blockhash" : "000000009ba667fe7e7d1da2a1e8aafe88404c87da43e0c03749f4ac75572961",
"blockindex" : 17,
"blocktime" : 1428923404,
"txid" : "73c24457fc2cbb463507fcaf3dcf31cb1a4e8d52e1e27ec4534d9c65c022aae9",
"walletconflicts" : [
],
"time" : 1428916502,
"timereceived" : 1428916502
},
{
"account" : "bitcoin",
"address" : "mzkKmWG9Sj4duFDzHQMvwEvt1S8f3K56sm",
"category" : "receive",
"amount" : 0.00114000,
"vout" : 0,
"confirmations" : 6,
"blockhash" : "000000009ba667fe7e7d1da2a1e8aafe88404c87da43e0c03749f4ac75572961",
"blockindex" : 15,
"blocktime" : 1428923404,
"txid" : "ebfbe3ea212190629fea63f1210d62c13a5dd31143beebecbb8465b351f0871e",
"walletconflicts" : [
],
"time" : 1428916516,
"timereceived" : 1428916516
},
{
"account" : "bitcoin",
"address" : "mzkKmWG9Sj4duFDzHQMvwEvt1S8f3K56sm",
"category" : "receive",
"amount" : 0.01000000,
"vout" : 0,
"confirmations" : 6,
"blockhash" : "000000009ba667fe7e7d1da2a1e8aafe88404c87da43e0c03749f4ac75572961",
"blockindex" : 10,
"blocktime" : 1428923404,
"txid" : "04e740d17ebbe31eb8522d0a3be2eebc2f19707225c1861cc19bf5751824d12e",
"walletconflicts" : [
],
"time" : 1428916521,
"timereceived" : 1428916521
},
{
"account" : "bitcoin",
"address" : "mzkKmWG9Sj4duFDzHQMvwEvt1S8f3K56sm",
"category" : "receive",
"amount" : 0.01000000,
"vout" : 0,
"confirmations" : 6,
"blockhash" : "000000009ba667fe7e7d1da2a1e8aafe88404c87da43e0c03749f4ac75572961",
"blockindex" : 16,
"blocktime" : 1428923404,
"txid" : "60edf9372117c53b24af7be847ecf125103b516379a1573ac87ca08e58402417",
"walletconflicts" : [
],
"time" : 1428916525,
"timereceived" : 1428916525
},
{
"account" : "bitcoin",
"address" : "mzkKmWG9Sj4duFDzHQMvwEvt1S8f3K56sm",
"category" : "receive",
"amount" : 0.02064000,
"vout" : 2,
"confirmations" : 5,
"blockhash" : "000000009700a992e9d76cda9c3b13c0236978d5cddae3de6eff74fd79e5c4f7",
"blockindex" : 18,
"blocktime" : 1428924605,
"txid" : "5b205c3428d9471c19866d992b20cf9c5cbc0f31757380773b44b41421c07464",
"walletconflicts" : [
],
"time" : 1428916706,
"timereceived" : 1428916706
},
{
"account" : "bitcoin",
"address" : "mzkKmWG9Sj4duFDzHQMvwEvt1S8f3K56sm",
"category" : "receive",
"amount" : 0.01921760,
"vout" : 2,
"confirmations" : 5,
"blockhash" : "000000009700a992e9d76cda9c3b13c0236978d5cddae3de6eff74fd79e5c4f7",
"blockindex" : 19,
"blocktime" : 1428924605,
"txid" : "f1dbd846c0c099121cebe9d79cb8befae6842ef96a9d89953192444a7aa3b959",
"walletconflicts" : [
],
"time" : 1428916708,
"timereceived" : 1428916708
},
{
"account" : "bitcoin",
"address" : "mzkKmWG9Sj4duFDzHQMvwEvt1S8f3K56sm",
"category" : "receive",
"amount" : 0.00681760,
"vout" : 2,
"confirmations" : 5,
"blockhash" : "000000009700a992e9d76cda9c3b13c0236978d5cddae3de6eff74fd79e5c4f7",
"blockindex" : 20,
"blocktime" : 1428924605,
"txid" : "9280235e76796d73b6f304fa67af64022991ba24e2db2317875cfb5ecc5b350d",
"walletconflicts" : [
],
"time" : 1428916709,
"timereceived" : 1428916709
}
] Second command: listtransactions bitcoin 100 6 [
{
"account" : "bitcoin",
"address" : "mzkKmWG9Sj4duFDzHQMvwEvt1S8f3K56sm",
"category" : "receive",
"amount" : 0.00100000,
"vout" : 0,
"confirmations" : 6,
"blockhash" : "000000009ba667fe7e7d1da2a1e8aafe88404c87da43e0c03749f4ac75572961",
"blockindex" : 17,
"blocktime" : 1428923404,
"txid" : "73c24457fc2cbb463507fcaf3dcf31cb1a4e8d52e1e27ec4534d9c65c022aae9",
"walletconflicts" : [
],
"time" : 1428916502,
"timereceived" : 1428916502
}
] I don't understand how "from" parameter works, Wiki says it's used to count from a certain number but there's everything messed up |
|
|
|
Hello fellows! I'm actually running bitcoind server to receive and send transaction through my own software. Transaction size of my spends are always near to 100kb/500kb, so how do I set a minimum/pseudo-fixed transaction fee in my bitcoin.conf/software? If you haven't figured out yet what I mean, I would always pay 0.0001 BTC for each spend cause they never exceed 1.000kb. Hoping in a fast reply You can't, the reference implementation wallet always pays some-amount-per-1000-bytes-of-the-transaction. The rules for the 0.10 release are: + By default, you always pay a fee (this is different from previous releases that would send transactions without a fee if they had high enough priority) (run with -sendfreetransactions=1 to get the old behavior of sending high-priority transactions without a fee) + By default, the fee-per-kilobyte is estimated based on recent transaction confirmation history. To get close to what you want (pay a fixed fee per transaction), run with -paytxfee=0.whatever : that tells the wallet code to pay 0.whatever BTC per 1000 bytes. Most transactions are about 500 bytes big. See here: http://core2.bitcoincore.org/smartfee/fee_graph.html ... for how high to make -paytxfee=0.whatever based on how long you're willing to wait for the first confirmation (that page graphs estimates from the latest&greatest fee estimation code from Alex Morcos that will hopefully be in the 0.11 Bitcoin Core release). I'm now having full control of fees through: - getbalance
- listunspent
- createrawtransactions
- signrawtransaction
- sendrawtransaction
Previous method was working fine but when change addresses (inputs) were too much I started spending more than 0.0001 BTC, complete chaos However now's everything ok with new functions |
|
|
|
Some mod please pin this at the top! Every newbie needs to see this!
This is a great idea, indeed it should be done "sticky" !  You just want to be known as the guy who has a sticky. You put jack shit effort into this thread and you think you're going to get stickied? Dream on. I would stick your post instead of it |
|
|
|
OH NICE TO KNOW, I WAS SO DUMB BEFORE.
*sarcasm mofos*
As i said, its for the ones who dont know ... mofo Well, you are actually FORCING them to do what you want. |
|
|
|
|
OH NICE TO KNOW, I WAS SO DUMB BEFORE.
*sarcasm mofos*
|
|
|
|
Another great feature added:
If your timer hasn't run out of time yet but there are already enough coins in our hot wallet to cover your payout, then you get instantly paid out. Rule is valid only for the players in actual position!
Looks like N9N, but that's great anyway. I would suggest you guys to put back collecting stats and fix countdown |
|
|
|
However I just have to use one address only hopefully eheh..
No. Typically you will need at least 2 output addresses for each transaction. You'll need the address that you are sending to, and you'll need an address under your control where you are sending the change. You'll need to make sure that you correctly calculate the change every time. If you send back too much change, then the transaction will be invalid and the entire network will reject your transaction. It will never confirm, and the person you are sending to will not receive the bitcoins that you are trying to send to them. If you don't send back enough change, then you will pay a ridiculously large transaction fee. Don't forget to calculate the transaction fee when determining the change. If you don't leave enough value in the transaction for an adequate transaction fee, then it may take a very long time for the transaction to confirm. Yes I understand, something like that: createrawtransaction '[{"txid":"d3be60aaf98ef888a9137928fa405806cd2e0c762f5205b3d9ba3e6ad26a5262","vout":1}]' '{"mxgxQ52kYRVPfLeYpXugkCAGhjLfUaZk3g":0.05000000,"mvDLEEymmEijZXyrrNRL3aPMhH8q2m8vE1":1.19994817}'Where first output is the receiving address and second one is my actual address receving back the rest minus fee. Am I right? |
|
|
|
Ok guys got it now, gonna use listunspent + createrawtransaction  Yes. If you use createrawtransaction, then you will have full control over exactly where the transaction value is assigned. Be VERY careful. Many knowledgeable and experienced people using createrawtransaction in the past have made typos or had bugs in their program that resulted in failing to send the change to an address, or sending the wrong amount of change to an address. Any unaccounted for transaction value (supplied by the inputs) will become transaction fees for the miner (or pool) that confirms your transaction. Thanks for the info, I'll try to work with it like a surgeon However I just have to use one address only hopefully eheh.. |
|
|
|
Ok guys got it now, gonna use listunspent + createrawtransaction |
|
|
|
|
Why is Bitcoin-QT/bitcoind automatically always sending bitcoins to weird addresses and then when you spend them are obviously spent from these weird addresses?
It's confusing!! You can't even track your actual balance on blockchain because bitcoins are in many weird addresses..... Btw I'm running a PHP software on testnet with sendtoaddress and sendmany functions.
|
|
|
|
HAPPY HOUR EVENT JUST STARTED!
For one hour only multiplier is set to x1.25 for new deposits.
how long the game ends  ??I don't think this game can end. It's similiar to N9N, if it collapses the game goes on if there are still users interested to play ofc. |
|
|
|
Suggest another happy hour and people become more active. BTW, have you noticed that most investors are in a time zone UTC+2, haven't you? You should hurry to think about it, because people will go to bed soon We are planning to do another happy hour tomorrow, but can't tell you more at the moment Very motivated Ponzi. As for N9N: congatz and keep it up hoe |
|
|
|
It seems to be promising. I would give it a try, seriously PS: website is responsive yes but not set for any display, please fix it. |
|
|
|
HourlyCoins actual statistics:
Total Investments: 4168
Total Payouts: 212149
Hey, guys, how many you lost in transaction fees? If 212149 * 0.0001 (standard transaction fee) it will be more 21 BTC! No you're wrong, they're sending many bitcoins to multiple outputs paying only 0.00000001 BTC per kilobyte. |
|
|
|
It's not a problem of N9N side, this is your fault! Are you using original Bitcoin Core? |
|
|
|
yes the speed is increasing again ... whoop whoop
Yes, i am in now ;-) You have almost reached 10 BTC of paid commissions, impressive goal nice guys!  |
|
|
|
|
Show Posts
