Show Posts
|
Pages: [1] 2 »
|
Peaty the pools/miners don't control the network, clients do. Miners won't mine a coin nobody uses.
|
|
|
I'm working hard on the bitcoin implementation right now, can't wait to see it in action either
|
|
|
Meaning what?
Nobody knows and the reddit threads that are created en masse smell of FUD and fake.
|
|
|
Have you read anything at all that I just posted? And if you didn't believe me, have you read through all the posts in the leak? What you just said is a complete fabrication supported by zero evidence. Maybe it is a fabrication, maybe not, I don't care much. I don't think blacklists will go anywhere because people are mixing their coins for privacy reasons anyway to avoid data mining by vendors, so coins connected to crime already spread through everyone's hands. I'm just saying that it's actually a good sign when the community shows clearly what they think about such ideas. Developers and entrepreneurs should not see this as an attack against themselves, but rather against the idea itself. After all, if no one plans anything evil it means that this is just a misunderstanding and all attacks are directed against foundation members in a parallel universe. And if such discussions didn't have to get leaked, people wouldn't immediately jump to the conclusion that something shady is going on. And if those leaks weren't in .zip format people would be able to check for themselves much easier.
|
|
|
imho any amount of backlash against such ridiculous ideas is justified, to show that this is a no-no. otherwise it will be like ACTA that is brought up again and again under different names.
and discovering that lobbyists are infiltrating the bitcoin foundation is worth a shitstorm of massive proportions too. I'm glad if the devs refuse to implement such things into bitcoin, but they won't be around forever and not everyone can resist bribes.
|
|
|
And if you own a company you pay a lower electricity price than regular people because the German government is corrupt like hell
|
|
|
JaSK recently asked: we can probably automate part of that process by communicating over bitmessage or direct p2p connections. But that will take more time and I'll have to ask FellowTraveler how he'd like it to be done.
The answer is: When a user wishes to move Bitcoins into OT, he will be sending the coins multi-sig, using your code as described above. As long as I am able to send and verify those coins, and as long as I am able to perform multi-sig votes to remove those coins back out, then I will be able to do the rest on the OT side. Bitmessage will not be needed for this, but if you want to get started on the Bitmessage integration, it's definitely needed for other pieces.I haven't had a proper look at the other parts of Moneychanger/OT yet so I'm not sure what we can and can't do. Just to clarify: As part of the escrow protocol each involved party has to share things like public keys, transaction ids, signed transactions,.. with each other via a secure communication channel. For testing we can just share those things via messenger and enter them in textboxes but that won't be very convenient or secure :p Is communication between the parties something I don't have to worry about?
|
|
|
I just ran into the same problem while working on the Moneychanger project for open-transactions. A solution is to use getrawtransaction <txid> to check if requested money was sent to the p2sh address in the first place, then getrawmempool to see if it has any confirmations yet, then getblockcount --> getblockhash(count) --> getblock(hash) --> getblock(block->previous) -->... to iterate through the blockchain to figure out how many confirmations it has. If you don't know the txid you could scan the blockchain for new txIDs and use getrawtransaction on each of them to figure out if any outputs were sent to the multi-sig address. Haven't implemented it yet so I'm not sure if it will work like this but so far it looks like it could imho. This all seems very hackish and error-prone to me so I hope we'll soon get proper bitcoin API support for that kind of transactions.
|
|
|
As you can see in my git history I managed to implement most of the required bitcoin api calls. We can now verify that certain transactions have been made (if we have the tx id) so my next step is to implement the actual escrow protocol. Iirc that requires just three more api functions (create-, sign- and sendrawtransaction) which shouldn't be difficult and some GUI elements and buttons. At the beginning this won't be very comfortable to use (addresses and tx ids will have to be shared and typed in manually) but we can probably automate part of that process by communicating over bitmessage or direct p2p connections. But that will take more time and I'll have to ask FellowTraveler how he'd like it to be done.
|
|
|
Yes, I meant ian, sorry. In Germany we spell it jan but pronounce it ian so my subconsciousness must've mixed that up :p Thanks for fixing the issue, I also think one active bid per task would probably be best.
|
|
|
I'm currently implementing the multi-sig-functionality, guess I'll get that done over the weekend, GUI elements will follow next week.
@fellowtraveler and @jan I think I can't place a new bid for the re-opened tasks on CIYAM because one can only apply once, so can you please enable them again for me? I'm making good progress with Bitcoin Integration (when I find time to work on it), Bitmessage is something someone else can work on but if nobody will I'll do it next.
|
|
|
I'm currently working on Bitcoin integration and will do Bitmessage next so I wouldn't mind if anyone does namecoin and colored coins in the meantime.
|
|
|
We're not holding anything for ransom. We don't get the coins until we finish a task and anyone is free to join the project and do it himself.
domob, I received my encrypted email when I registered but you can also change the address to https:// which will allow you to register without PGP key. Edit: What is your Namecoin-OTR-Plugin going to do?
|
|
|
marcus_of_augustus, if you want someone with more free time on his hands to code it, you'll have to do it yourself or add to the bounty until you attract more programmers or until it pays enough to work on the project full time. the only thing that's not going to help is bitching.
btw as you can see on github, I started coding (not related to your bitching though!).
|
|
|
hey, I'm one of the people working on the holy grail tasks. Sorry, but so far I've not done much yet I set up the dev environment and started playing around a bit but due to lots of real-life stuff and needing a holiday I haven't done much real work on it yet. However I do have free time and skills, so don't worry, I just had some higher priority tasks to take care of first Just wanted to give you a status update from my side, from what I saw Xenland is working hard on his tasks.
|
|
|
Had my last day of work yesterday so I'll be able to start developing holy grail code full-time now. Good luck with BitShares and have fun, bytemaster
|
|
|
How would the Integration with legacy banking be done? Do we initiate the SEPA transaction via some sort of API or do we just tell the user to "go to his banking site and send money to XYZ"? Why are you guys donating so much money for this?
60btc for three(?) programmers is actually pretty low payment, even if we manage to finish it in one month (not very likely considering the amount of beta-testing required for such an application)
|
|
|
Registered without problems, seems like a great service.
Question to fellowtraveler: Are the Project Task Delivery dates final or did you just fill in a random date?
Minor glitch report to CIYAM: When I write a note when bidding for a task I have to escape commas to not get an error message. Bla bla bla\, blablabla.
|
|
|
Hello everyone I wasn't able to post earlier because of the must-be-5-hours-online-rule but I claimed Bitmessage or/xor Bitcoin multisig via email. bytemaster aparently has some interest in the bitmessage part so if it's alright with everyone I'll do the multisig integration?.. My GitHub nick is tuttleorbuttle but there's nothing to see yet apart from a few tests that show that I'm new to Git :p
|
|
|
|