Show Posts
|
Pages: « 1 2 [3] 4 5 »
|
Is bitcoinmonitor.net reliable when it comes to notifications? (does it crash often/miss some transactions/etc) Is it advisable to use this service in a real-world e-commerce site? If not what other robust transaction notification APIs (apart from bitcoind) are out there?
|
|
|
I know "litecoinj" is not "bitcoinj" but rather an incomplete hack from it. Nonetheless I need some help and could not find it in other places. I cannot get it to connect/download the blockchain (SPV mode). Here is the log: 1472597 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [71.95.226.206]:9333 - Connection refused: no further information 1472748 [New I/O worker #1] INFO com.google.litecoin.core.TCPNetworkConnection - Announcing to dnsseed.litecoinpool.org/72.81.129.238:9333 as: /LitecoinJ:0.8-SNAPSHOT/PingService:1.0/ 1472748 [New I/O worker #1] DEBUG com.google.litecoin.core.LitecoinSerializer - Sending version message: fbc0b6db76657273696f6e00000000007e000000e10c6d7661ea00000000000000000000244a9a5200000000000000000000000000000000000000000000ffff7f0000012475000000000000000000000000000000000000ffff7f00000124750000000000000000282f4c697465636f696e4a3a302e382d534e415053484f542f50696e67536572766963653a312e302f0f27000000 1473464 [New I/O worker #1] INFO com.google.litecoin.core.Peer - [72.81.129.238]:9333 - An existing connection was forcibly closed by the remote host 1473717 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [59.32.166.126]:9333 - connection timed out 1474617 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [173.246.29.218]:9333 - connection timed out 1475517 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [2.121.74.139]:9333 - connection timed out 1476217 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [173.209.174.113]:9333 - connection timed out 1476391 [New I/O worker #7] INFO com.google.litecoin.core.TCPNetworkConnection - Announcing to dnsseed.litecoinpool.org/144.76.203.217:9333 as: /LitecoinJ:0.8-SNAPSHOT/PingService:1.0/ 1476391 [New I/O worker #7] DEBUG com.google.litecoin.core.LitecoinSerializer - Sending version message: fbc0b6db76657273696f6e00000000007e000000fe7d03b061ea00000000000000000000294a9a5200000000000000000000000000000000000000000000ffff7f0000012475000000000000000000000000000000000000ffff7f00000124750000000000000000282f4c697465636f696e4a3a302e382d534e415053484f542f50696e67536572766963653a312e302f0f27000000 1476572 [New I/O worker #7] INFO com.google.litecoin.core.Peer - [144.76.203.217]:9333 - An existing connection was forcibly closed by the remote host 1477117 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [184.94.227.58]:9333 - connection timed out 1477118 [pool-47-thread-2] WARN com.google.litecoin.discovery.DnsDiscovery - Unable to resolve dnsseed.bytesized-vps.com 1478017 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [86.170.83.143]:9333 - connection timed out 1478617 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [72.224.31.142]:9333 - connection timed out 1483148 [pool-47-thread-3] WARN com.google.litecoin.discovery.DnsDiscovery - Unable to resolve dnsseed.ltc.xurious.com 1487119 [New I/O worker #5] INFO com.google.litecoin.core.PeerGroup - Peer discovery took 10002msec 1489618 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [184.56.123.216]:9333 - connection timed out 1489618 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [109.190.113.198]:9333 - connection timed out 1489619 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [24.128.195.182]:9333 - connection timed out 1492118 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [79.188.120.226]:9333 - connection timed out 1492118 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [82.75.135.156]:9333 - connection timed out 1492119 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [86.136.153.108]:9333 - connection timed out 1492445 [New I/O worker #7] INFO com.google.litecoin.core.TCPNetworkConnection - Announcing to dnsseed.litecoinpool.org/131.96.40.221:9333 as: /LitecoinJ:0.8-SNAPSHOT/PingService:1.0/ 1492446 [New I/O worker #7] DEBUG com.google.litecoin.core.LitecoinSerializer - Sending version message: fbc0b6db76657273696f6e00000000007e000000e44088fc61ea00000000000000000000394a9a5200000000000000000000000000000000000000000000ffff7f0000012475000000000000000000000000000000000000ffff7f00000124750000000000000000282f4c697465636f696e4a3a302e382d534e415053484f542f50696e67536572766963653a312e302f0f27000000 1493146 [New I/O worker #2] INFO com.google.litecoin.core.TCPNetworkConnection - Announcing to dnsseed.litecoinpool.org/24.165.116.111:9333 as: /LitecoinJ:0.8-SNAPSHOT/PingService:1.0/ 1493146 [New I/O worker #2] DEBUG com.google.litecoin.core.LitecoinSerializer - Sending version message: fbc0b6db76657273696f6e00000000007e000000e44088fc61ea00000000000000000000394a9a5200000000000000000000000000000000000000000000ffff7f0000012475000000000000000000000000000000000000ffff7f00000124750000000000000000282f4c697465636f696e4a3a302e382d534e415053484f542f50696e67536572766963653a312e302f0f27000000 1493542 [New I/O worker #2] INFO com.google.litecoin.core.Peer - [24.165.116.111]:9333 - An existing connection was forcibly closed by the remote host 1493775 [New I/O worker #3] INFO com.google.litecoin.core.TCPNetworkConnection - Announcing to dnsseed.litecoinpool.org/185.18.44.168:9333 as: /LitecoinJ:0.8-SNAPSHOT/PingService:1.0/ 1493775 [New I/O worker #3] DEBUG com.google.litecoin.core.LitecoinSerializer - Sending version message: fbc0b6db76657273696f6e00000000007e00000042fce94b61ea000000000000000000003a4a9a5200000000000000000000000000000000000000000000ffff7f0000012475000000000000000000000000000000000000ffff7f00000124750000000000000000282f4c697465636f696e4a3a302e382d534e415053484f542f50696e67536572766963653a312e302f0f27000000 1493888 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [71.95.226.206]:9333 - Connection refused: no further information 1494619 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [84.45.237.230]:9333 - connection timed out 1494677 [New I/O worker #5] INFO com.google.litecoin.core.TCPNetworkConnection - Announcing to dnsseed.litecoinpool.org/72.81.129.238:9333 as: /LitecoinJ:0.8-SNAPSHOT/PingService:1.0/ 1494677 [New I/O worker #5] DEBUG com.google.litecoin.core.LitecoinSerializer - Sending version message: fbc0b6db76657273696f6e00000000007e00000042fce94b61ea000000000000000000003a4a9a5200000000000000000000000000000000000000000000ffff7f0000012475000000000000000000000000000000000000ffff7f00000124750000000000000000282f4c697465636f696e4a3a302e382d534e415053484f542f50696e67536572766963653a312e302f0f27000000 1495108 [New I/O worker #2] INFO com.google.litecoin.core.Peer - [79.188.120.226]:9333 - An existing connection was forcibly closed by the remote host 1495385 [New I/O worker #5] INFO com.google.litecoin.core.Peer - [72.81.129.238]:9333 - An existing connection was forcibly closed by the remote host 1495918 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [59.32.166.126]:9333 - connection timed out 1497118 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [2.121.74.139]:9333 - connection timed out 1497118 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [173.246.29.218]:9333 - connection timed out 1497299 [New I/O worker #3] INFO com.google.litecoin.core.TCPNetworkConnection - Announcing to dnsseed.litecoinpool.org/144.76.203.217:9333 as: /LitecoinJ:0.8-SNAPSHOT/PingService:1.0/ 1497299 [New I/O worker #3] DEBUG com.google.litecoin.core.LitecoinSerializer - Sending version message: fbc0b6db76657273696f6e00000000007e0000000d77ee5b61ea000000000000000000003e4a9a5200000000000000000000000000000000000000000000ffff7f0000012475000000000000000000000000000000000000ffff7f00000124750000000000000000282f4c697465636f696e4a3a302e382d534e415053484f542f50696e67536572766963653a312e302f0f27000000 1497418 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [184.94.227.58]:9333 - connection timed out 1497481 [New I/O worker #3] INFO com.google.litecoin.core.Peer - [144.76.203.217]:9333 - An existing connection was forcibly closed by the remote host 1497482 [pool-48-thread-2] WARN com.google.litecoin.discovery.DnsDiscovery - Unable to resolve dnsseed.bytesized-vps.com 1498418 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [173.209.174.113]:9333 - connection timed out 1499418 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [86.170.83.143]:9333 - connection timed out 1499421 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [72.224.31.142]:9333 - connection timed out
|
|
|
here is the log of the run. http://pastebin.com/6bQ1yP2d#I know the devs will tell not to use it as they are working on a better version. But I need it now. My only need is to broadcast raw tx. The rest of the stuff need not work. Please tell me what to change in the litecoinj source to get it to connect. I think there is some issue with dns seeds. 1472597 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [71.95.226.206]:9333 - Connection refused: no further information 1472748 [New I/O worker #1] INFO com.google.litecoin.core.TCPNetworkConnection - Announcing to dnsseed.litecoinpool.org/72.81.129.238:9333 as: /LitecoinJ:0.8-SNAPSHOT/PingService:1.0/ 1472748 [New I/O worker #1] DEBUG com.google.litecoin.core.LitecoinSerializer - Sending version message: fbc0b6db76657273696f6e00000000007e000000e10c6d7661ea00000000000000000000244a9a5200000000000000000000000000000000000000000000ffff7f0000012475000000000000000000000000000000000000ffff7f00000124750000000000000000282f4c697465636f696e4a3a302e382d534e415053484f542f50696e67536572766963653a312e302f0f27000000 1473464 [New I/O worker #1] INFO com.google.litecoin.core.Peer - [72.81.129.238]:9333 - An existing connection was forcibly closed by the remote host 1473717 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [59.32.166.126]:9333 - connection timed out 1474617 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [173.246.29.218]:9333 - connection timed out 1475517 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [2.121.74.139]:9333 - connection timed out 1476217 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [173.209.174.113]:9333 - connection timed out 1476391 [New I/O worker #7] INFO com.google.litecoin.core.TCPNetworkConnection - Announcing to dnsseed.litecoinpool.org/144.76.203.217:9333 as: /LitecoinJ:0.8-SNAPSHOT/PingService:1.0/ 1476391 [New I/O worker #7] DEBUG com.google.litecoin.core.LitecoinSerializer - Sending version message: fbc0b6db76657273696f6e00000000007e000000fe7d03b061ea00000000000000000000294a9a5200000000000000000000000000000000000000000000ffff7f0000012475000000000000000000000000000000000000ffff7f00000124750000000000000000282f4c697465636f696e4a3a302e382d534e415053484f542f50696e67536572766963653a312e302f0f27000000 1476572 [New I/O worker #7] INFO com.google.litecoin.core.Peer - [144.76.203.217]:9333 - An existing connection was forcibly closed by the remote host 1477117 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [184.94.227.58]:9333 - connection timed out 1477118 [pool-47-thread-2] WARN com.google.litecoin.discovery.DnsDiscovery - Unable to resolve dnsseed.bytesized-vps.com 1478017 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [86.170.83.143]:9333 - connection timed out 1478617 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [72.224.31.142]:9333 - connection timed out 1483148 [pool-47-thread-3] WARN com.google.litecoin.discovery.DnsDiscovery - Unable to resolve dnsseed.ltc.xurious.com 1487119 [New I/O worker #5] INFO com.google.litecoin.core.PeerGroup - Peer discovery took 10002msec 1489618 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [184.56.123.216]:9333 - connection timed out 1489618 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [109.190.113.198]:9333 - connection timed out 1489619 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [24.128.195.182]:9333 - connection timed out 1492118 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [79.188.120.226]:9333 - connection timed out 1492118 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [82.75.135.156]:9333 - connection timed out 1492119 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [86.136.153.108]:9333 - connection timed out 1492445 [New I/O worker #7] INFO com.google.litecoin.core.TCPNetworkConnection - Announcing to dnsseed.litecoinpool.org/131.96.40.221:9333 as: /LitecoinJ:0.8-SNAPSHOT/PingService:1.0/ 1492446 [New I/O worker #7] DEBUG com.google.litecoin.core.LitecoinSerializer - Sending version message: fbc0b6db76657273696f6e00000000007e000000e44088fc61ea00000000000000000000394a9a5200000000000000000000000000000000000000000000ffff7f0000012475000000000000000000000000000000000000ffff7f00000124750000000000000000282f4c697465636f696e4a3a302e382d534e415053484f542f50696e67536572766963653a312e302f0f27000000 1493146 [New I/O worker #2] INFO com.google.litecoin.core.TCPNetworkConnection - Announcing to dnsseed.litecoinpool.org/24.165.116.111:9333 as: /LitecoinJ:0.8-SNAPSHOT/PingService:1.0/ 1493146 [New I/O worker #2] DEBUG com.google.litecoin.core.LitecoinSerializer - Sending version message: fbc0b6db76657273696f6e00000000007e000000e44088fc61ea00000000000000000000394a9a5200000000000000000000000000000000000000000000ffff7f0000012475000000000000000000000000000000000000ffff7f00000124750000000000000000282f4c697465636f696e4a3a302e382d534e415053484f542f50696e67536572766963653a312e302f0f27000000 1493542 [New I/O worker #2] INFO com.google.litecoin.core.Peer - [24.165.116.111]:9333 - An existing connection was forcibly closed by the remote host 1493775 [New I/O worker #3] INFO com.google.litecoin.core.TCPNetworkConnection - Announcing to dnsseed.litecoinpool.org/185.18.44.168:9333 as: /LitecoinJ:0.8-SNAPSHOT/PingService:1.0/ 1493775 [New I/O worker #3] DEBUG com.google.litecoin.core.LitecoinSerializer - Sending version message: fbc0b6db76657273696f6e00000000007e00000042fce94b61ea000000000000000000003a4a9a5200000000000000000000000000000000000000000000ffff7f0000012475000000000000000000000000000000000000ffff7f00000124750000000000000000282f4c697465636f696e4a3a302e382d534e415053484f542f50696e67536572766963653a312e302f0f27000000 1493888 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [71.95.226.206]:9333 - Connection refused: no further information 1494619 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [84.45.237.230]:9333 - connection timed out 1494677 [New I/O worker #5] INFO com.google.litecoin.core.TCPNetworkConnection - Announcing to dnsseed.litecoinpool.org/72.81.129.238:9333 as: /LitecoinJ:0.8-SNAPSHOT/PingService:1.0/ 1494677 [New I/O worker #5] DEBUG com.google.litecoin.core.LitecoinSerializer - Sending version message: fbc0b6db76657273696f6e00000000007e00000042fce94b61ea000000000000000000003a4a9a5200000000000000000000000000000000000000000000ffff7f0000012475000000000000000000000000000000000000ffff7f00000124750000000000000000282f4c697465636f696e4a3a302e382d534e415053484f542f50696e67536572766963653a312e302f0f27000000 1495108 [New I/O worker #2] INFO com.google.litecoin.core.Peer - [79.188.120.226]:9333 - An existing connection was forcibly closed by the remote host 1495385 [New I/O worker #5] INFO com.google.litecoin.core.Peer - [72.81.129.238]:9333 - An existing connection was forcibly closed by the remote host 1495918 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [59.32.166.126]:9333 - connection timed out 1497118 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [2.121.74.139]:9333 - connection timed out 1497118 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [173.246.29.218]:9333 - connection timed out 1497299 [New I/O worker #3] INFO com.google.litecoin.core.TCPNetworkConnection - Announcing to dnsseed.litecoinpool.org/144.76.203.217:9333 as: /LitecoinJ:0.8-SNAPSHOT/PingService:1.0/ 1497299 [New I/O worker #3] DEBUG com.google.litecoin.core.LitecoinSerializer - Sending version message: fbc0b6db76657273696f6e00000000007e0000000d77ee5b61ea000000000000000000003e4a9a5200000000000000000000000000000000000000000000ffff7f0000012475000000000000000000000000000000000000ffff7f00000124750000000000000000282f4c697465636f696e4a3a302e382d534e415053484f542f50696e67536572766963653a312e302f0f27000000 1497418 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [184.94.227.58]:9333 - connection timed out 1497481 [New I/O worker #3] INFO com.google.litecoin.core.Peer - [144.76.203.217]:9333 - An existing connection was forcibly closed by the remote host 1497482 [pool-48-thread-2] WARN com.google.litecoin.discovery.DnsDiscovery - Unable to resolve dnsseed.bytesized-vps.com 1498418 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [173.209.174.113]:9333 - connection timed out 1499418 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [86.170.83.143]:9333 - connection timed out 1499421 [New I/O boss #9] INFO com.google.litecoin.core.Peer - [72.224.31.142]:9333 - connection timed out
|
|
|
I keep hearing rumors.. Is this true?? When did this happen?
|
|
|
Can you guy share your ideas on how to implement off-chain games that are provably fair. I'm looking more at the provably fair part. If it helps, consider a dice game.
As an unrelated question: On-chain games like satoshidice and likes have bloated the chain from 2gb to 13gb in a year. What is the future? Are we looking at 1 TB in a few years?
EDIT: posted in wrong forum. Wanted to do in "Dev and tech support". Can mods move?
|
|
|
I had 0.0025 BTC on inputs.io. When I filed my claim from the same email address registered, I get the following email: Hi,
We've identified this request as suspicious based on proprietary rules. In order to protect the amount against fraudulent claims, please attach a copy of a government issued photo ID matching your name. This is used for verification purposes only. Why should I provide identification? Very fishy. How about Tradefortress first provide his identifying information??
|
|
|
Hi Mike, Any plans to add feature to get list of unspent outputs for a given address? (Address is not in wallet). Technically this information should be there in every client. Even bitcoind currently does not allow such a query though, so if you implement it, bitcoinj will be "ahead" of bitcoind... How hard is this to add? Perhaps you can give me pointers to which files to look at.
|
|
|
I have tried the latest build of bitcoinj and get error signing messages containing non-ascii characters. This problem also occurs with older versions. Here is the string. C'est par mon ordre et pour le bien de l'Etat que le porteur du présent a fait ce qu'il a fait.This is the default string on brainwallet verify tabWhen I use the com.google.bitcoin.core.ECKey.signMessage() method to try to sign this message. I get an exception "array index out of bound". This works nicely if the string contains only ASCII characters. So if we remove the é from the above string, things work fine. Hope this is fixed soon. Cheers!
|
|
|
Swim made a BFL order sometime in Apr/May 2013 for a single. Will (s)he be able to get a refund from BFL now? If yes, whats the process.
|
|
|
Offer can be closed any time at my discretion. I can do escrow. Accept method: only bank transfer (HDFC)
Please pm or post here to discuss/negotiate.
|
|
|
Please pm or post here. Can do escrow. Require bank transfer to HDFC bank.
|
|
|
I want to sell one or two btc via bank transfer. Please pm or post here. Transfer to hdfc bank. Mt gox rate
sold
|
|
|
I want to report a successful deal with lassdas. Took a leap of faith for a largish amount and he delivered. I sent first.
|
|
|
OTC is a place where we can buy/sell bitcoins "over the counter". The Web-of-Trust (WoT) is a system used by OTC to rate and give reputation to buyers and sellers. Negative reputation means not very trustworthy, and more positive means more trustworthy (to a degree, since a lot of positive raters could themselves be negatively rated, so you got to check a bit more before trusting). This explains in details. http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otchttp://wiki.bitcoin-otc.com/wiki/OTC_Rating_Systemhttp://wiki.bitcoin-otc.com/wiki/Bitcoin_address_authenticationYou can use otc with bitcoin-qt or Blockchain.info (you need to be able to sign messages) This way we can trade btc without depending on exchanges. The reputation system will allow us to do trades without issues. Some suggested fiat payment in india to use on otc. 1. Paypal (not sure if it works INR -> INR domestic) 2. Bank transfer NEFT/RTGS 3. Mobile pay (MPay??) 4. Ghar pay 5. Mobile recharges 6. Pizza delivery 7. Shopping / vouchers (Flipkart/Infibeam/etc) 8. ... others ... ? (please add)
|
|
|
Please pm me. Only well rated users. For Eur, prefer someone in Germany. Done!
|
|
|
Please pm me. Only people with rep please.
Also please let me know how much time it will usually take. Also English only. My German is very rusty.
|
|
|
Please pm me if interested. Can buy less as well.
buying at 100 USD per BTC.
|
|
|
I had some funds in MtGox, and I didn't execute any trade. I was planning to get that 1 BTC back. However when I logged in just now, I realized my 1 BTC has become 0.989... BTC I found this to be strange (well not much stranger than funds disappearing on other exchanges) I went to trade history and sure enough there was a trade that I didn't do. How is this possible? I have 2FA so there were no withdrawls.
|
|
|
There was MtGox DDoS, then the "crash", then BTC-e got hacked or something, then bitcoin-24 is down due to some stuff. Whats going on?
|
|
|
Please also post why you think its the worst.
|
|
|
|