You can always use a small script to parse on of the many available api's... I wrote a startscript that *should* work for address with a history <= 50 tx's. It could easily be expanded for > 50 tx's by putting everything in a loop and make requests to the api changing the to-parameter untill the response is not containing anymore data... It's also quite easy to convert the unix timestamp to a readable date, and things might go sour if the amount of numbers in the timestamp differs between the transactions (in other words, all transactions have to be BEFORE 09/09/2001 or after 09/09/2001... Fixing this issue would also be pretty easy, but as i said: i'm feeling lazy today... And since bitcoin didn't exist in 2001, it shouldn't matter anyway) This script is open source, free and NOT intended for production environments... I did not ask blockexplorer.com's permission to use their api, and i only tested the script on one of my own addresses... I was to lazy to build a proper testcase... I'm not responsible for any damages you might incur running this script ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) import requests import json import collections address = '1YourAddressHere' URL = "https://blockexplorer.com/api/addrs/"+address+"/txs?from=0&to=50" r = requests.get(url = URL) database = json.loads(r.text) outputdb = {} for item in database['items']: txid = item['txid'] timestamp = item['time'] vins = item['vin'] vouts = item['vout'] for vin in vins: vinaddr = vin['addr'] valuein = vin['value'] if vinaddr == address: value = valuein * -1 outputdb[str(timestamp) + '.' + str(txid)] = {"txid": str(txid), "timestamp": int(timestamp), "value" : float(value)} for vout in vouts: try: voutaddresses = vout['scriptPubKey']['addresses'] voutvalue = vout['value'] for voutaddress in voutaddresses: if voutaddress == address: outputdb[str(timestamp) + '.' + str(txid)] = {"txid": str(txid), "timestamp": int(timestamp), "value" : float(voutvalue)} except: number = 1 od = collections.OrderedDict(sorted(outputdb.items())) balance = 0 for k, v in od.iteritems(): balance = balance + float(v['value']) print str(v['timestamp']) + ' ' + str(v['txid'] + "=> " + str(balance) + "<" + str(float(v['value'])) + ">")
|
|
|
I did comment in some of those threads, but I just took a look at what's available and a lot of the threads deal with politics, and I detest politics so much so that I stopped watching television around 2001 and have never followed political discussion on the internet and barely keep up with what's going on in the world. That's just me, but I am a hermit and enjoy my blissful ignorance of the assholes in power and what they're doing to destroy us all. Other topics in Ivory Tower dealing with tech like "bricking" a phone or the New Zealand digital strip search I read with interest but didn't feel qualified enough to comment on. Not sure why Ivory Tower and Serious Discussion haven't caught on like I thought they would, but there are some good threads there from time to time that I post in. Maybe it's too political? Maybe the amount of discussion being had is too thin? Who knows, but I shall kiss your bald head in appreciation of your efforts to keep the Tower alive. Same here ^^ Most of the time i spend on bitcointalk, i'm trying to help people with technical problems, problems with development, meta questions, and i try to learn the technical background of new crypto based technologies. The last time i looked at the ivory tower, it was completely filled with threads that didn't look interesting to me... It's just a matter of personal taste, but i couldn't bring myself to start reading those threads... It's perfectly possible somebody else might be interested, and i'm sure the people participating in those threads have a good time, and enjoy spam-free threads. However: i'd need a completely different kind of OP to start participating in the ivory tower.
|
|
|
Hi, i just send a transaction of 0.00012 bitcoin, and a fee of 200 satoshis, and now appears only unconfirmed, two hours and still nothing, i think i gonna change my wallet, anyone know how fix this pls? ![Embarrassed](https://bitcointalk.org/Smileys/default/embarrassed.gif) Well, there are 2 possibility's: 1) your transaction IS unconfirmed 2) your transaction is confirmed, but there's a problem with your wallet (depends on which wallet you're using) The first possibility is the most likely. The fee isn't based on the value of the transaction, but on it's size (in bytes). A transaction using 4 inputs of 0.0001 BTC and one output is much larger than a transaction using 1 input of 100 BTC and one output (given they're the same kind of transaction: P2SH, P2PKH, segwit,...)... So the first transaction has a value of 0.0001 BTC but needs a fee that's about 3-4 times higher than the second transaction with a value of 100 BTC. At any rate, a 200 sat fee seems low to me... even if you are using a wallet that's natively using bech23 addresses and only have one input and one output. Your options: 1) waiting it out 2) bump the fee (if the tx was opt-in RBF) 3) a CPFP 4) double spending the inputs of the unconfirmed tx 5) paying a miner to include your tx in the block he's currently working on (only works if the miner solves this block, don't pay some random dude that's trying to convince you he'll mine the transaction for you... Most of these guys are scammers)
|
|
|
I guess you'll have hundreds of applicants IF and only IF you escrow this 1 ETH x the number of applicants.
Step 1) Search a reputable forum escrow Step 2) Send him x ETH Step 3) Ask the escrow to sign a message proving he/she is holding x ETH for this "campaign"
|
|
|
You may have that problem just cuz you`re using not secure resources. I can suggest you to use bitcoin mixer for transfers and mixing various bitcoins. It`s secure and anonymous. hmmm ![Roll Eyes](https://bitcointalk.org/Smileys/default/rolleyes.gif) bob123 was completely correct, NeuroticFish was mostly correct (unconfirmed transactions should show up in electrum's history)... But Bitexpert11's sollution shows that he's not a Bit expert (pun intended). I've never heared about the mixer that's being linked to (this doesn't mean anything, exept that it might not be a popular mixer), but more important: using a mixer has nothing to do with transactions not showing up in your wallet's history. As a matter of fact, using a mixer is just adding an extra variable in the mix. A mixer is usefull if you want to break the link between the senders and your wallet... To repeat the previous posters: - Verify if the transaction exist on a block explorer and is funding the address you entered while withdrawing
- Double check if the address is correct
- Change the electrum server by clicking the button in the right bottom corner
- Make sure you have an official electrum version (check the signature of ThomasV)
- Make sure you have the latest electrum version
- Make sure a local firewall isn't blocking you (either a firewall on your pc, or on your own network)
- Restart your wallet and reboot your pc
If nothing else works, but you are sure your address is correct, and a funding tx exists, you can always download a clean electrum copy on a new device that's on a different network, and restore your wallet from seed...
|
|
|
I might sound like an ass for saying this, but in reality i'd never invest my money into somebody who hasn't been active in the community (unless we're talking about very reputable people that have earned their reputation somewhere else). I had to work for every satoshi i own, so i'm rather carefull with how i spend my coin... I realise a lot of longtime members might also scam you, but at least they've invested a lot of time into their online reputation. If the sum of the invested funds is smaller than the amount of money an individual would have made with an IRL job during the time they were active on the forum, i think it *should* make them more trustworthy than the opposite scenario.
What i did in the past was analyse projects developed by new member and give feedback on what they're doing, but i would never go as far as endorsing a project by somebody i've never heared off.
|
|
|
From --help output piratecashd [options] <command> [params] Send command to -server or piratecashd
you need specify help without --
Got it now... It works, thanks!
|
|
|
--snip--
piratecashd is cli utility too. Without parameters it will run daemon and with it you will see outputs like coinmame-cli (i'll split cli and daemon in future realises)
--snip--
Are you sure? running piratecashd --help gives the following output: ./piratecashd --help Piratecash version v1.0.1.3-60010
Usage: piratecashd [options] piratecashd [options] <command> [params] Send command to -server or piratecashd piratecashd [options] help List commands piratecashd [options] help <command> Get help for a command
Options: -? This help message -conf=<file> Specify configuration file (default: piratecash.conf) -pid=<file> Specify pid file (default: piratecashd.pid) -datadir=<dir> Specify data directory -wallet=<dir> Specify wallet file (within data directory) -dbcache=<n> Set database cache size in megabytes (default: 10) -dbwalletcache=<n> Set wallet database cache size in megabytes (default: 1) -dblogsize=<n> Set database disk log size in megabytes (default: 100) -timeout=<n> Specify connection timeout in milliseconds (default: 5000) -proxy=<ip:port> Connect through SOCKS5 proxy -tor=<ip:port> Use proxy to reach tor hidden services (default: same as -proxy) -dns Allow DNS lookups for -addnode, -seednode and -connect -port=<port> Listen for connections on <port> (default: 23232) -maxconnections=<n> Maintain at most <n> connections to peers (default: 125) -addnode=<ip> Add a node to connect to and attempt to keep the connection open -connect=<ip> Connect only to the specified node(s) -seednode=<ip> Connect to a node to retrieve peer addresses, and disconnect -externalip=<ip> Specify your own public address -onlynet=<net> Only connect to nodes in network <net> (IPv4, IPv6 or Tor) -discover Discover own IP address (default: 1 when listening and no -externalip) -irc Find peers using internet relay chat (default: 0) -listen Accept connections from outside (default: 1 if no -proxy or -connect) -bind=<addr> Bind to given address. Use [host]:port notation for IPv6 -dnsseed Query for peer addresses via DNS lookup, if low on addresses (default: 1 unless -connect) -forcednsseed Always query for peer addresses via DNS lookup (default: 0) -synctime Sync time with other nodes. Disable if time on your system is precise e.g. syncing with NTP (default: 1) -banscore=<n> Threshold for disconnecting misbehaving peers (default: 100) -bantime=<n> Number of seconds to keep misbehaving peers from reconnecting (default: 86400) -maxreceivebuffer=<n> Maximum per-connection receive buffer, <n>*1000 bytes (default: 5000) -maxsendbuffer=<n> Maximum per-connection send buffer, <n>*1000 bytes (default: 1000) -upnp Use UPnP to map the listening port (default: 0) -paytxfee=<amt> Fee per KB to add to transactions you send -mininput=<amt> When creating transactions, ignore inputs with value less than this (default: 0.01) -testnet Use the test network -debug=<category> Output debugging information (default: 0, supplying <category> is optional) If <category> is not supplied, output all debugging information. <category> can be: addrman, alert, db, lock, rand, rpc, selectcoins, mempool, net, coinage, coinstake, creation, stakemodifier. -logtimestamps Prepend debug output with timestamp -shrinkdebugfile Shrink debug.log file on client startup (default: 1 when no -debug) -printtoconsole Send trace/debug info to console instead of debug.log file -regtest Enter regression test mode, which uses a special chain in which blocks can be solved instantly. This is intended for regression testing tools and app development. -rpcuser=<user> Username for JSON-RPC connections -rpcpassword=<pw> Password for JSON-RPC connections -rpcport=<port> Listen for JSON-RPC connections on <port> (default: 3535) -rpcallowip=<ip> Allow JSON-RPC connections from specified IP address -rpcconnect=<ip> Send commands to node running on <ip> (default: 127.0.0.1) -rpcwait Wait for RPC server to start -rpcthreads=<n> Set the number of threads to service RPC calls (default: 4) -blocknotify=<cmd> Execute command when the best block changes (%s in cmd is replaced by block hash) -walletnotify=<cmd> Execute command when a wallet transaction changes (%s in cmd is replaced by TxID) -confchange Require a confirmations for change (default: 0) -alertnotify=<cmd> Execute command when a relevant alert is received (%s in cmd is replaced by message) -upgradewallet Upgrade wallet to latest format -createwalletbackups=<n> Number of automatic wallet backups (default: 10) -keypool=<n> Set key pool size to <n> (default: 100) (litemode: 10) -rescan Rescan the block chain for missing wallet transactions -salvagewallet Attempt to recover private keys from a corrupt wallet.dat -checkblocks=<n> How many blocks to check at startup (default: 500, 0 = all) -checklevel=<n> How thorough the block verification is (0-6, default: 1) -loadblock=<file> Imports blocks from external blk000?.dat file -maxorphanblocks=<n> Keep at most <n> unconnectable blocks in memory (default: 750)
Block creation options: -blockminsize=<n> Set minimum block size in bytes (default: 0) -blockmaxsize=<n> Set maximum block size in bytes (default: 250000) -blockprioritysize=<n> Set maximum size of high-priority/low-fee transactions in bytes (default: 27000)
SSL options: (see the Bitcoin Wiki for SSL setup instructions) -rpcssl Use OpenSSL (https) for JSON-RPC connections -rpcsslcertificatechainfile=<file.cert> Server certificate file (default: server.cert) -rpcsslprivatekeyfile=<file.pem> Server private key (default: server.pem) -rpcsslciphers=<ciphers> Acceptable ciphers (default: TLSv1.2+HIGH:TLSv1+HIGH:!SSLv3:!SSLv2:!aNULL:!eNULL:!3DES:@STRENGTH) -litemode=<n> Disable all Darksend and Stealth Messaging related functionality (0-1, default: 0)
Masternode options: -masternode=<n> Enable the client to act as a masternode (0-1, default: 0) -mnconf=<file> Specify masternode configuration file (default: masternode.conf) -mnconflock=<n> Lock masternodes from masternode configuration file (default: 1) -masternodeprivkey=<n> Set the masternode private key -masternodeaddr=<n> Set external address:port to get to this masternode (example: address:port) -masternodeminprotocol=<n> Ignore masternodes less than version (example: 61401; default : 0)
Darksend options: -enabledarksend=<n> Enable use of automated darksend for funds stored in this wallet (0-1, default: 0) -darksendrounds=<n> Use N separate masternodes to anonymize funds (2-8, default: 2) -anonymizepiratecashamount=<n> Keep N Piratecash anonymized (default: 0) -liquidityprovider=<n> Provide liquidity to Darksend by infrequently mixing coins on a continual basis (0-100, default: 0, 1=very frequent, high fees, 100=very infrequent, low fees)
InstantX options: -enableinstantx=<n> Enable instantx, show confirmations for locked transactions (bool, default: true) -instantxdepth=<n> Show N confirmations for a successfully locked transaction (0-9999, default: 10) Secure messaging options: -nosmsg Disable secure messaging. -debugsmsg Log extra debug messages. -smsgscanchain Scan the block chain for public key addresses on startup.
to be honest, these look like standard daemon startup options, i don't see any info on how to run 'common' cli commands like creating new addresses, sending funds, looking at the mempool or the outputs,...
|
|
|
hello.my hdd crashed so i cant even open it.the last proggram testdisk looking good if u have similar problem.i also tried to contact hotmail support to find the deleted backup link but the recovered emails was till january 2018 and the delete date was previous.
I ll let u know if i recover it
So i take it you didn't follow my initial advice and clone the disk straight away? If you did follow my advice, you should have a clone image of your original disk, so it shouldn't matter if it crashed...
|
|
|
Good luck with your new project... I checked it out and installed it on my sandbox system... I did have 2 remarks tough: - I couldn't get the sourcecode compiled, so i chose to use the precompiled linux binaries... However, i'm missing some tools here. The tar.gz contains the daemon and the QT, but i'm missing piratecash-cli so i can execute cli commands against a running daemon
- Your website is still talking about running minerd and cpu-mining, i set everything up for a short solo-mine, but at current diff, it's nearly impossible to do this... I guess your network has a couple GPU or ASIC miners, making it nearly impossible to cpu mine. I'd rather see this option removed from your website TBH
For the rest, it looked nice, and i'll probably be following your development
|
|
|
--snip--
I will wait sync to see if appears the info, thank you.
no problem ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) you should wait at least untill the blocks of 2016 were downloaded and parsed. If you don't see incoming transactions by the time you see your wallet caught up all the blocks of 2016, something else might be wrong... But, if you had funds in your wallet in 2016, the odds are good that they'll show up as soon as the blocks funding your addresses are downloaded
|
|
|
1) is the wallet finished syncing? 2) core does not ask for a password, even when the wallet itself is locked. You can run core with a locked wallet and generate new addresses. It's only when you want to spend funds you'll have to unlock your wallet (there are some other functions you can't use unless you unlock your wallet, but a lot of functionality is available without unlocking)
If it's a non-HD wallet (this might be the case for a ~2016 wallet), the wallet should contain pregenerated private keys. If , you use the gui, you should be able to create a new deposit address, this address should have been the same address as was generated in the past. You can check this address on a block explorer and see if it was funded.
I'd advise you to backup the encrypted wallet.dat, then let bitcoin core sync completely and see if transactions start to show up in your transaction history... If they do, you should be able to unlock your wallet using your password and spend these funds...
|
|
|
--snip-- As far as Electrum goes, its a lightweight wallet, meaning it won't take that long for it to synchronized as you don't need download the current Bitcoin blockchain size. As for Bitcoin core, its different though, there is a way called pruning. wherein it will allows one to run a smaller version of full blockchain. For technical questions for Electrum, you can go visit this board: Electrum. For Bitcoin Core, you can post your questions here, Development & Technical Discussion. @bL4nkcode, have said, don't worry about your money, you just need to wait until it goes full sync. running core in pruning mode does not cut down syncing times... It only saves diskspace! You have 2 problems: core syncing and electrum syncing Electrum syncing should not take more than 5-10 minutes, since you only download the block headers... If it takes longer than a couple of hours, you can have one of the following problems: 1) connected to a "bad" node 2) network problems on your side 3) running an old, or bad version of electrum the sollutions to these problems 1) click on the green/organge/red button at the bottom right corner, disable automatic server selection and pick a different server 2) check your own router, firewall,... 3) make sure you downloaded electrum from electrum.org and check ThomasV's sig A last sollution that can always be tried in general is: downloading the latest version, installing it on a different pc, restore your wallet from the seed phrase, stop the wallet, reboot the pc, restart the pc, load the wallet again and see if it works now... Core syncing Core will download more than 200 Gb of data (blocks). It will verify each and every block, and all transactions in every block. It will build a utxo dabase and constantly update it... This takes time... A good CPU, sufficient memory, an SSD and fast internet might cut down this syncing time, but you can never expect your wallet to be fully sync'd in less than a day (and such a synctime would require a really expensive dedicated server) If you have really, really good reasons for which you HAVE to HAVE access to your funds, there are ways to export your private keys and import them into an SPV wallet (like electrum). Offcourse, you'd have to solve your electrum syncing problem first...
|
|
|
Basically yes, I would like to create a hot wallet, but didn't really think that it is called "hot". Are there any tutorials or resources how to make an Electrum-based hot wallet on server?
If you install any full, funded wallet (be it core, electrum, btcd,...) on an online webserver and use it to automatically handle payouts, it is per defenition a hot wallet. You can find info about the json rpc interface: http://docs.electrum.org/en/latest/merchant.html
|
|
|
I am looking for if we implement a bitcoin mining device can increase our transaction speed?. Right now we are not running any mining at the moment. Short answer: no. If you want faster transactions, you'll have to increase the fees you use. If you want blocks to be found faster, running your own mining hardware isn't going to change that at all. Thank you for your update. Is there any way I can track my current bitcoin incoming transaction speed? There is no such thing as 'incoming transaction speed'. Transactions are broadcasted trougout the network in a matter of seconds. If your fee (in sat/byte) is in the top 1 mb in the current mempool, you have a decent chance your tx will end up in the next block. I'm on my phone right now, if somebody didn't give you a full explanation by tomorrow morning, i'll try to explain in detail when i get in at work tomorrow morning..
|
|
|
Whether or not and under what circumstances my own mining machine would be faster than professional miners?
It's quite hard to understand what you're asking exactly. Do you want to know wether or not you'll be able to make the ASIC you purchased run faster? In this case, you can experiment with the alternative firmware that's available for some of the bitmain products. You can also overclock your ASIC and/or make sure it runs in an optimal environment (heat, moisture, dust, fast network, low latency pool connection,...). This being said, using alternative firmware and overclocking *might* harm your hardware... So do it at your own risk. Also, overclocking *might* result in more hashes per second, however, the amount of Joules per Terrahash that's being used might also rise (costing you a lot more in power). It's perfectly possible that your ASIC running at 13.5 Th/s draws 1300 Watt, while the same ASIC running at 13.7 Th/s draws 1600 Watts (imaginary numbers)
|
|
|
Thanks for the tip with watch only wallet. The thing is - I also need to send bitcoins from Electrum. Would this cold wallet solution, perhaps with some modifications, work for sending or a completely different approach is neede then?
Sure, you can use your watch-only wallet to create unsigned transactions, then transfer them to your cold wallet for signing and back to your watch-only wallet for broadcasting. Or, you can just install electrum on a 100% clean desktop PC that can actually connect to the internet, generate a new seed (write it down), export the xpub to your server for a watch only wallet. In this case, you can just spend your funds from the electrum wallet on your online desktop PC.. Offcourse, this setup is less secure than a real cold wallet. A different, safer, sollution would be to use a hardware wallet and export it's xpub (and import it on your watch-only wallet on your server). This way, you could spend your funds by using your hardware wallet ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
|
|
Just a remark here... Wouldn't it be easyer to run electrum as a daemon and create a watch only wallet by importing the cold wallet's xpub? This way the online electrum daemon would derive addresses from the xpub, but there would be no way for a hacker to rob you, since the xprv is only stored in an offline machine. This setup will save you a lot of headache, time and fees... I know this doesn't answer your questions directly, i was merely trying to give you a different perspective... Sometimes we get caught up in a sollution that's stuck in our mind without considering there might be better sollutions to begin with ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
|
|
can we ran this electrum daemon if we have pruned bitcoin core(prune=5000)
also, can you point the link for electrum daemon?
yes, electrum can be run next to core, eventough i'm wondering why you'd use electrum if you're also running bitcoin core... I have no experience with btcpayserver, but if it's using core in the background i wonder if btcpayserver is also able to handle payouts if you import the xprv instead of the xpub??? If not, you should be able to import the xprv into the bitcoin core instance you're running anyways and use core's json-rpc interface to handle payouts (i've never done this myself, but iirc, it should be possible, altough i don't know if the derivation path is the same between both implementations???) Here's the link you were asking for: http://docs.electrum.org/en/latest/merchant.html
|
|
|
im using btcpay server. It allowed me to insert my xpub (created using elctrum) and generate deposit addresses. Detecting payments using nbxplorer.
Im pretty new to bitcoin, but I think I understand the basic of it. xpub=masterpublic key, xprv=masterprivate key.
So now for receiving payment I use btcpayserver that create millions of deposit addresses from my masterpublic key and directly sync with my elctrum.
now for payment I need to create a new wallet?
First things first, you are right: xpub = master public key, which can be used to derive deposit addresses xprv = master private key, which can be used to derive private keys, these private keys can be used to calculate the public key, the public key can be hashed to generate the address I have never used btcpayserver, but if you created a wallet by entering your xpub, it's a watch-only wallet, so yes, you'll need a different wallet to handle payouts. What you could do is use the electrum wallet from which you exported the xpub, if it's a "real" wallet (generated from a seed or an xprv), it should keep track of the same addresses as generated by your btcpayserver, so if you run electrum as a daemon, it should be able to function as a hot wallet. If you run btcpayserver and electrum on the same machine, you might aswell directly import the xprv in btcpayserver? I don't know how safe btcpayserver is since i have never used it tough!
|
|
|
|