Ahh, makes my mind sit at ease now heh.
Good to hear. The other thing I should have mentioned is that you should also probably delete the keys from your database after you export them so that the next exportation operations don't include all the keys you have already exported because it will become quite slow when you have a lot of keys. |
|
|
|
Also, if this a one and done import to blockchain or something that needs to be done everytime a seller wants to collec funds ? Every new transaction will create with it a new private key to hold the funds of that transaction, so you can't just do it once. So for every litteral transaction, the previously stated steps need to be done ? There's no way to batch it ? Seems kinda suckish if someone does 20 transactions in one day and has to do all those steps for each and every one. You don't need to follow those steps for every transaction. The steps I described allow you to export all your private keys at once. It is a batch export in a sense, but once new keys get added to your database then you will need export those new keys (which can be done as batch also). The reason for having a new address for every transaction is because it's recommended practice in order to provide increased anonymity to buyers, and also because of the way transactions are processed, it requires each new address to start off with an empty balance. If it used just a single address then it would be very hard to separate the transactions and work out who paid what without having the bitcoind server installed. |
|
|
|
Also, if this a one and done import to blockchain or something that needs to be done everytime a seller wants to collec funds ? Every new transaction will create with it a new private key to hold the funds of that transaction, so you can't just do it once. |
|
|
|
|
For importing your keys into blockchain.info wallet:
1. Login to admin area
2. Got to Orders
3. Select MANAGE KEYS
4. Select EXPORT KEYS
5. Input private RSA key when prompted
6. Scroll down and copy text from "Blockchain.info Format" box
7. Log into Blockchain.info wallet
8. Select "Import / Export" from top menu
9. Select "Import Wallet" from side menu
10. Paste text from step 6 into box and select "Import Wallet"
|
|
|
|
|
Ok, I think I have a good plan for how I can add Tor support without compromising the security of regular clients. Before making the transaction the buyer will have an option to select whether or not they are using Tor or any other service which will cause their IP address to constantly change, and they will be warned of the security implications if they choose that option (that it makes session hijacking attacks possible unless the website is secured with an SSL certificate).
|
|
|
|
Hey bitfreak! When someone order one thing, then send BTC, then close the window without confirmation (it's common case), the order won't be send to buyer. In the admin panel there's option to confirm that payment. After that the e-mail should be sent to buyer, but it isn't. I mean it should be sent to buyer's e-mail, then change 'Processing' status to 'Completed'. Could you improve it? Thank you.
Yes I'll try to add that fix to a future release. What I really want to do is create a way for the user to continue the transaction if they come back to the shop website (they should get a notice saying they haven't finished their transaction properly). The problem with that idea though is I need to use cookies, and that re-opens the door for session hijacking attacks once again. But if I want to support Tor users I don't really think there is any way to protect against session hijacking apart from the site having an SSL certificate to protect the transmission of cookies. |
|
|
|
Bitfreak, I understand pretty much everything on the install.txt file you gave in the release but I have no idea how to use the mysql_db.txt you described, could you give clearer instructions on that? Normally I'm used to PHP stuff being needed on the Cpanel which I've already set up but I'm not sure what to do here.
steamgames pretty much explained what you need to do. You need to create a new database and then use the mysql_db.txt to create the new tables. Watch the installation video (link in the client file area) if you still cannot figure it out. |
|
|
|
I am presuming that the proof chain needs to go back at least as far as the most recent "hard checkpoint" known to the client. IE, the client can occasionally trim the oldest blocks from the proof chain, but only after a software update that gives it a later checkpoint to work from. Correct. I'm also presuming that a "hard checkpoint" will be added to the client only when no blockchain reorg that reaches previous to that checkpoint is still acceptable or possible. The "hard checkpoint" will hardly ever be updated because the proof chain will remain tiny for very for long periods of time. |
|
|
|
I'm going to try to as well. But will use it for my altcoin.
I would highly recommend that you try to team up with Cryddit. There will be less wasted effort and things will get done quicker if you guys team up instead of working independently. 'Probably' does have a point about that. |
|
|
|
Someone stated "Devs are hard to find" in the thread. This is absurd.
Developers are typically not hard to find, but when you require developers skilled enough to work on cutting edge crypto-currency technology which has never been built before, it is very hard to find developers. In the many months I've been advertising this bounty, Cryddit is actually the only person who has told me directly that he is going to try to implement this concept in order to claim the bounty. EDIT: and if developers don't want to waste their time attempting to claim this bounty, then they should try to team up with other developers in this thread who have already said they are working in it. |
|
|
|
Just imagine I do not redeem my casascius coin for 50 years. Will it become worthles? Maybe I want to treasure some "paper wallets" in a time capsule.
In that case your coins would get re-mined under the assumption they were lost. You would have to transfer a portion or all of your coins to another address to prove that you still have control of the coins. |
|
|
|
It wouldn't be hard at all to make it easy to reference an account by address alone. That would make it equally simple to just ignore some extra data called an "offset" as being something I don't really need to find the account -- unless you mean that you also want to be able to look it up by offset alone, without needing the address for this other kind of search?
I didn't write that part of the wiki, but I think you're correct, we should only need to reference an account by the address. The first option seems more sensible to me, because the only idea that causes "recovery" to make any sense is the presumption that the private key to the address has been lost. Coins recently sent to that address do not indicate that it has been found. Yes exactly, you are right about this as well. If it was done the other way then anyone could send coins to an address to ensure that the coins are never considered to be lost, which would defeat the purpose of the re-mining system. |
|
|
|
|
Sounds like a plan, we can discuss the details further when I return, for now I need to get some shut eye. I'll be back to check on this thread later.
|
|
|
|
|
I was thinking about that too, but multisig transactions require all parties to agree before the funds can be released, and I really don't want any more than 2 parties involved, so I'm not really sure there's a point. If we both hold a portion of the funds then the winner of the bounty can at least be fairly certain they will receive a partial reward from one of us.
|
|
|
|
|
Ok after some thinking I am willing put some of the project funds under the control CIYAM Open (I'm thinking 10 BTC), but I will maintain control of the rest of the funds. I know I don't have any trust feedback but I have been a part of this forum since early 2011 and have been offering bitcoin related tools and information on my website for many years, so I think I have earned some trust in any case.
|
|
|
|
I was just looking at the Nxt coins and I noticed that it has removed scripts from the system. Nxt doesn’t use so-called “scripts” aka predicates. This simplifies and accelerates transaction processing. Anyone looking to implement this idea should take a look at Nxt because the mini-blockchain wont use script either (scripts are impossible due to the way the Account Tree works). |
|
|
|
|
Thanks for the encouragement, I'm just not very optimistic anymore because I've been trying to find developers for this project for many months now. And this thread was already on the 5th page of the alt-coin section before I even noticed it was moved, which is extremely discouraging. Gaaahhh I guess I'll just have to suck it up and hope for the best.
|
|
|
|
Great... moved to the alt-coin section. Now this thread has every chance in the world of being noticed by decent developers...  |
|
|
|
I'm working on a similar idea, but with only two components: account tree and proof chain. Also writing in python. Project is progressing, should be done in a few month.
Not really interested in the bounty.
Well it does not necessarily have to be written in one of the languages I specified. If you can get the basic concept implemented without the extra components you will still be eligible for the first bounty. |
|
|
|
You would be welcome to create a project on CIYAM Open Thanks for the offer, but the problem is finding developers skilled enough to work on a project like this. That's why I created a bounty in the first place, because I found it very difficult to put together a team of developers skilled enough to work on this project. If there is a team of developers out there who think they can get the job done then I am more than willing to that route. And I will also keep your escrow offer in mind, because you strike me as some one I can trust to get the job done. |
|
|
|
|
Show Posts
