 Show Posts
|
|
Pages: [1] 2 3 4 5 6 »
|
EDIT: I'm stupid. theymos seems to be right. It's Adblock Plus. Attentive users may have noticed that a new CSS rule has been added to the site, causing all cex.io links in signatures (and maybe posts, I have not tested) to be hidden: ::content a[href^="https://cex.io/"] {display:none;}Would an admin mind explaining the rationalee for this. In addition, it should be noted that this can be bypassed simply by changing the capitalisation of "cex.io". |
|
|
|
if your scared, this reveals many things:
1) your relying on an online service for something that causes you emotional distress if lost
2) your relying on an third party for something that causes you emotional distress if lost
3) you cannot be arsed to double check your balance using a different option
i think its time you reviewed your lapse in security. and get a proper bitcoin wallet program....
if anyone else is getting worried about blockchain.info balance issues. then you too should realise that you have obviously more than 'disposable' income stored in a online third party service. and then do something about it
It's not only about personal wallets, it's about businesses using blockchain.info API.  But you are right, it's definitely time to switch to other platform. Have a look at https://bitcointalk.org/index.php?topic=605737 (my project to develop a new blockchain explorer. See http://www.reddit.com/r/Bitcoin/comments/279ssy/dont_panic_blockchaininfo_is_not_connected_to_the/ for more info about the Blockchain.info situation. |
|
|
|
Hey BitcoinTalk! Just thought I'd show you all my latest invention. Node-ECIES is a Node.js implementation of ECIES, a little known elliptic curve encryption system using ECDH and a Symmetric Cipher (not sure which one, maybe AES). What that means in English, is that given a Bitcoin address' public key, you can encrypt messages to it. Now, this is not all my work, all I did was put a wrapper around node-cryptopp, which in turn is a set of bindings for Crypto++. What I did do is figure out how to use node-cryptopp to do ECIES. Note that you can't send messages to bitcoin addresses, only to public keys, which are available if the user has sent bitcoins from their address. You can query for the public key by doing: https://blockchain.info/q/pubkeyaddr/1Bardi4eoUvJomBEtVoxPcP8VK26E3AyxnUsage:var bitcoin = require('bitcoinjs-lib'),
ecies = require('ecies');
var text = 'Secret ECIES Test Message!';
/* sha256('correct horse battery staple') */
var publicKey = '0478d430274f8c5ec1321338151e9f27f4c676a008bdf8638d07c0b6be9ab35c71a1518063243acd4dfe96b66e3f2ec8013c8e072cd09b3834a19f81f659cc3455';
var privateKey = bitcoin.ECKey('5KJvsngHeMpm884wtkJNzQGaCErckhHJBGFsvd3VyK5qMZXj3hS').toHex();
var cipherText = ecies.encrypt(text, publicKey, 'secp256k1');
var decryptedText = ecies.decrypt(cipherText, privateKey, 'secp256k1');
console.log(text, '->', cipherText, '->', decryptedText);
And of course, where would I be without a selfish request for donations. Coins sent to the address in the signature pay for me to create implementations in different languages. Have a nice day. |
|
|
|
I current run https://apicoin.io, and we have push tx functionality ( https://apicoin.io/api/v1/doc/#pushtx). We are also the currently the only ones that can do it in batch, up to 100 signed transactions in one api call. We use special technology that we designed to do that, so you aren't going to load up any premade software to do that. Are you dreaming?  Minimum 4 GB per coin and perhaps more. And use load balancing  I would assume we could cope with a DigitalOcean $10/month (1GB RAM, 1 Core, 30GB Disk, 2TB Transfer) Also this impossible, you would need at least 75GB. But then I wouldn't also use that same VPS for the frontend otherwise you will be running very slow. Blockchain is 17.3GB. Even with a indexes and everything it shouldn't need more than 30GB, or am I wrong. Not sure what "special technology" you use, but submitting txs to the network is very simple. I'm aware that there is not much " premade software" for blockchain explorers, at least not very good ones, hence the "Need Devs" title. At this rate it seems I'll just have to develop it myself. What are the qualifications for this job?
And how much would you pay ?
Not sure if I was explicit enough in the OP. I'm looking for some people who want to be part of the project and get a share of profit or donations. (I am broke.) |
|
|
|
Fck off.... $19/year is what the topic says. I hope no1 "donates" to you.
Somehow read that as $19/month, hence the comment. I've deleted it. Massive apologies. |
|
|
|
I want to add Litecoin and Dogecoin to libbitcoin. Might be a month or so before it happens, but we want this in DW and SX.
Right now I have to focus on optimising the blockchain.
Great to hear from you. If you need any help, just say the word. I'm going to try and con someone into paying for a VPS. =) |
|
|
|
Hi BitcoinTalk, Thought I might see if there is any interest in creating a new blockchain explorer like Blockchain.info for Bitcoin, Litecoin and any other big alt-coins. It would have a wallet system similar to Blockchain.info, but with one crucial difference, it would support multiple crypto-currencies. This allows you to stop lugging around ten (or more) different damons and blockchains for all your favorite altcoins, but most of all, it stops dumb/lazy (I'm the latter  ) people having all your money in Crypsy, just waiting for another Inputs.io fiasco. Before you say that blockchain explorers already exist, I've yet to come across one with pushtx functionality (other that Blockchain.info). And before the alt-coin haters come and throw rocks, I'd just like to say that all the alt-coins are interesting experiments with different parameters and algorithms, and I'd hate to see a alt-coin that could have been the future fall over from lack of support. All coins should have access to the same services like pools, blockchain explorers and wallets. From my research, an obelisk server seems to do what we need it too. Add that to a Node.js front end and you have your service. The trickiest part is porting Libbitcoin and Obelisk to Litecoin/etc. SHA256 coins should be relatively simple as I think it's just some genesis block, magic byte and address prefix changes. I'm thinking that starting the Bitcoin one first would be a good idea, as it would give us experience with Obelisk before we tackle the challenge of If anyone is interesting in helping, don't be shy, post below. Oh, and the other thing is what sort of specs would you need for hosting? I would assume we could cope with a DigitalOcean $10/month (1GB RAM, 1 Core, 30GB Disk, 2TB Transfer) for now (for Bitcoin). Hopefully someone will fund us to get better servers (hint hint). Hope this all made sense, late at night here but thought I should get this out sooner than later.  TL;DR: I want to create something like Blockchain.info for multiple crypto-currencys (BTC/LTC/DOGE/maybe more?). |
|
|
|
The website has been updated to include a message from the admin: Important message from the admin:
The Pool now supports compressed key solutions. We will also be phasing out additive solutions soon, so make sure to keep your miners up to date.
Would someone mind explaining what all this business about additive/multiplicative/compressed key solutions is. I also saw this: I'm 100% sure oclvanityminer is searching for patterns belonging to only a single public key at once, and this implies the multiplicative method (if I understand correctly). Still, I don't know if it is actually using that method.
There have been a lot of questions lately about additive vs. multiplicative, and how they work in oclvanitygen/oclvanityminer. I'll try to answer them. Oclvanityminer uses the additive method: - Generate a random partial private key
- Calculate the associated partial public key
- Add the base public key to the partial public key to get the test public key
- Generate a large batch (~1M) of sequential addresses by successively adding the generator point to the test public key, and converting the points to addresses
- If a match is found, report the partial private key plus the number of times the test public key was incremented. Otherwise, repeat the previous step
Sequential public keys in this scheme are generated by successively adding the generator point to the test public key. In the multiplicative method, we would skip adding the base public key to the test key at the start, and use the base public key as the increment instead of the generator point. If anyone really wants to use the multiplicative method instead, it's possible to modify oclvanityminer to do this by changing maybe 5-10 lines of code. The performance difference would be negligible. You are correct that oclvanityminer will search for addresses belonging to a single public key at a time. I'm not sure how additive vs. multiplicative makes a difference in the ability to concurrently search for patterns using different base public keys. For that matter, I'm not quite sure how to efficiently search for multiple patterns with different base public keys in the first place. Which is confusing me. I thought the system went like this: - Generate a random partial private key
- Calculate the associated partial public key
- Add the base public key to the partial public key to get the address public key
- Use RipeMD160 and Base58 to check the address. Repeat.
I'm not really on top of ECDSA and this is really confusing. Any help is appreciated. |
|
|
|
|
ETA on 0.9 Stable? Only interested because I'm running an altcoin that I want to upgrade the code of and want to get the best base code possible.
|
|
|
|
Just got back online. Damnit. and zedcoin? what the hell is zedcoin? picardwtfisthisshit.jpg Anyway, here for the long haul  , .78+ BTC poorer  Did you donate even more to mintpal? :O I need valid node IPs, my wallet isn't syncing.
The ones in OP are working, let the wallet be open for a few min and it should sync Can you give me the dump of your getpeerinfo (debug window)? Thanks. |
|
|
|
|
I need valid node IPs, my wallet isn't syncing.
|
|
|
|
We took your favorite pool of all time and made it compatible with you favorite coin of all time. Here is the result. P2Pool for Galtcoin! What is P2Pool?P2Pool is a decentralized pool that works by creating a P2P network of miner nodes. These nodes work on a chain of shares similar to Bitcoin's blockchain. Each node works on a block that includes payouts to the previous shares' owners and the node itself. There is no central point of failure, making it DoS resistant. For information is available on their homepage, wiki page or GitHub. Getting and setting up P2Pool + GaltcoinSetup P2Pool as normal (see wiki page) with the following exceptions: Linux Startup Command: nohup python p2pool/run_p2pool.py --net galtcoin --give-author 0 -f pool_fee_for_public_node > logs/p2pool.log & NOTE: To see stats, go to http://localhost:10334/ NOT http://localhost:9333/List of all blocks found: http://www.galt-explorer.com/address/1Kz5QaUPDtKrj5SqW5tFkn7WZh8LmQaQi4 (978 at time of writing!) self == lazy (public node list)HELP!If you run into trouble, don' hesitate to give me a yell. I hang out in the #galtcoin room at Loquacious (CoinChat) or you can PM me, start an issue on GitHub or send me an email at: nospamplease [at] bardiharborow [dot] tk |
|
|
|
|
Objection your honor! Alt-coin section needs to stay, case closed. End of story.
|
|
|
|
I'm looking to create a new wallet. I could do it all myself, but I figured there would be someone out there who would like to help. Requirements: - Can we please have a wallet that looks nice, something like HiveWallet.
- A choose around fees. Yes you can chuck as many warnings as you want but get let us have the final choice!
- Relay headers over a P2P network (i'm told some SPV wallets already do this)
- Improved security via spot-checks (explained here but the hash bit is gibberish to me, there must be a simpler way that doesn't require changes to blocks).
- It would be nice for balance lookups (ie. getting all relevant TX) to go through the p2p network to either full nodes or to lots of spot-checking nodes.
- Support for multiple cryptocurrencys. Cryptocurrencys would be added through a config file with chain params, checkpoints, address format, etc... You many have them on seperate p2p networks or have peers shared through 1 central network.
- Operate a JSON RPC daemon with either the current bitcoind calls or a improved set (I've always found them to be clunky).
- Feel free to add to this list.
Hopefully someone won't point out two minutes after I post this that what I want already exists, well that would be good, but it would be embarrassing. I would try to improve and expand this post, but I think it serves it's purpose, which is to get a discussion going. |
|
|
|
Nice, but not new ideas. Here's the most recent thread on "fraud proofs": https://bitcointalk.org/index.php?topic=137933.0. For "partial verification", we'd need TXO commitments by miners. Mark Friedenbach (maaku) recently implemented authenticated prefix trees for this, and Peter Todd has proposed an alternative data structure -- a so called Merkle mountain range (MMR) -- that may be more efficient. Can you clarify what you mean by "TXO commitments"? Can't we just have SPV clients do spot-checks (including tracing back to when the coin was generated) and if they find an invaild tx they send a invaild_alert(txhash) type alert? SPV wallets already work the way you suggest. I first proposed Bloom filters in 2011 and they were implemented and launched at the start of 2013. These wallets (multibit/android/hive etc) already download the headers from the p2p network too. So good thinking but I'd suggest doing more research before proposing other ideas that were already implemented years ago Well that is embarrassing... I looked at the only SPV wallet that doesn't use a p2p network (electrum). When I mentioned merkle hashes I believe I was suggesting using them in a different way than currently but I could be wrong. Also, you didn't mention my "partial verification" idea (turns out someone stole it first, not maybe I can't call it my idea  ), my understanding is that has not been implemented (feel free to correct me). |
|
|
|
Blockchain.info is stuborn. I'm thinking of editing the code to change this, but until that happens, try making a custom tx with http://brainwallet.org/ (sadly only lets you use use 1 from address). |
|
|
|
|
Centralisation - The dread of (almost) every Bitcoin user, but we are currently on track to do just that. Even the bitcoin.org website recommends a SPV client. So, I've done some thinking and have come up with as system that will allow the whole Bitcoin network to operate on a form of SPV network and still be decentralised. I'm not going to go into what SPV is. See Satoshi's white-paper for info. Here is my idea:
Each client will first download the headers, just like in Electrum, but with one crucial difference, it will download them fro a p2p network. After verifying them and working out the best tip, it will then begin to download some of the transactions. Notice I said "some". It will randomly download a percentage of the transactions (the percentage being set by the user, those who want to run full nodes download 100%, for example I might download 1%, about 130 MB). The transactions it gets will then be verified. If it finds invalid transactions it ignores the block and sends out an alert to the network. Then everyone in the network downloads the tx, verifies it, notices that it is invalid and discards the block.
Think of this as each node running random spot checks on transactions and raising the alarm if it finds a problem. People who download a percentage help support the network, and ensure that no transactions are ever lost.
The other idea I had was to use a bloom filter to notify peers of what txs you had (can somebody tell me whether that is a possibility?).
I believe this would require a new protocol to implement. Therefore, we would get bitcoind owners to run this as well to keep both networks synced.
Hope this is of interest, if so give me a yell and I'll start to get a dev team together (volunteers welcome).
|
|
|
|
|
