Well then, now we have:
5Juu2CkB3-----EcyH9dypNh-----gh6RQwwbo5ueBa6------
We need to figure out which section has one that needs an extra space. Because now we don't know which ones need 6 characters.
Then number 10 can be 7 letters and the last character of the Private key is E
|
|
|
Server will go down briefly for a quick code update. Please ignore any errors about "Remote Procedure Call failed" in the next few minutes.
|
|
|
Please wait. You are number 3 in the queue.
What is this ??
And its not updating on mobile version I am using in google chrome browser in mobile
Just wait. You are the third person in the queue. It must process each request one at a time to avoid being ip banned by Bitcointalk. Depending on the account, it can take from a few seconds to a few minutes to work, so just wait and be patient for it to work. Nice Stuff !! My account worth 0.189BTC , As i am also a coder i would suggest you to disable view state as i can see two stuffs at the same time "User ID must only be numbers Please wait. You are number 1 in the queue."
What did you do to cause that? Firstly i by mistake typed the name instead of Profile ID and it gave me the error"User ID must only be numbers" and again after seeing this error i just typed my profile id and all went fine , just want you to disable Enableviewstate so that once any user input any wrong stuffs and again he enters a right choice he should not see the previous error message as i saw in previous. Good Luck ! Thanks, I fixed the problem and will push the fix out soon.
|
|
|
Nice Stuff !! My account worth 0.189BTC , As i am also a coder i would suggest you to disable view state as i can see two stuffs at the same time "User ID must only be numbers Please wait. You are number 1 in the queue."
What did you do to cause that?
|
|
|
Great work! I just tested with my account and it found my account's estimated value in less than 15 seconds. I do have one suggestion regarding the ads. The top banner ad looks a little out of place, maybe if you centered it that would make it look a little better? Huh. It looks centered to me. What browser are you using? But overall great work, the only other thing maybe worth tweaking a little bit is the formula for finding the account value, it estimated that my account is worth ~ 0.12 BTC. I'd estimate that it would actually be worth 0.07 BTC or so at most, since Senior Member accounts seem to be selling for fairly cheap here now ( < 0.2 BTC).
I have noticed the decreasing prices and I will soon adjust the estimation accordingly.
|
|
|
Even if I didn't have a sig campaign, I would still be on this forum, albeit posting less frequently. Still, there are many ways to get Bitcoin from this forum through providing services and selling things, so I wouldn't leave.
|
|
|
My website is up and usable at http://www.bctalkaccountpricer.info/The site is very simple, just enter the User ID and it will do everything for you. There is a queuing system in place to prevent the server from being IP banned by Bitcointalk. The site will let you know where you are in the queue and will automatically retrieve all of the information when it is your turn. There are a few notable differences between the website version and the version on github: - Ads - The website has ads to help me support the site. I did not include the code for the ads in the github
- IP wait times - The website will require you to wait 5 minutes before it will let you submit another request. This is to prevent DoS attacks on the site. The Github contains the code for this, but it is commented out.
- Account bot password - In order for the website to work, an account is required to view the trust of members. The Github has a placeholder password THAT DOES NOT WORK while the website has the correct password.
If you have issue with any of the above, please let me know and see if we can fix the problem. If you find any bugs in the website, please contact me here or using the issue tracker on Github.
|
|
|
After reading through the OP it seems that you are looking this in a manner that seems to be over complicated and bothersome for the average consumer of said 'file'.
There is a much simpler approach to this.
A trusted website where a producer of a 'file' can upload said 'file' to the website. This file is then sold via the website, the buyer get's the link to the purchase page from the seller. Once on this page he clicks "buy now" (or something to that effect) a unique bitcoin address is generated and the buyer is asked to transfer the asking price for the 'file' to this address, after a certain number of confirmations the file is released and the buy can download said 'file'.
The seller can have automatic withdrawals set up so that once a product has been bought and confirmed through the website. The BTC that was sent is then forwarded to the seller minus whatever commission the site is charging for providing this service.
The file contents would also be verified by the operators of the website and there is a review system so that buyers can review the file they have bought.
There are already sites that do this, but what the OP is doing is going for a trustless approach. Your suggestion (also widely used) requires trusting a third party. They have to trust that that third party doesn't read the contents of the files, and for the third party to release the file to the buyer and to release the funds to the seller. The trustless system suggested here is to remove that middleman who is also collecting commission. It allows the buyer and seller to buy and sell files while also giving an incentive to not scam.
|
|
|
If you want to anonymize your Bitcoin, then just sending all of them to another wallet of yours is not very safe. You should use a mixing service. They will make it more difficult to trace the Bitcoin.
|
|
|
I don't see how it could be a firewall issue. I've been running Bitcoin-Qt for years with no problem from this same iMac.
How do I navigate to the "debug console"? I don't see it.
The firewall could be blocking connections to and from the program. To get to the debug console, go to Help > Debug Console. It should tell you how many connections you have. If it has some connections, click on the Peers tab and see if the peers are actually connected. If they are connected the ping time should NOT be N/A. If it is N/A, then something is wrong.
|
|
|
Have you tried restarting insight or clearing its databases to resynce? That might help, otherwise, I don't know if what the problem is. Also, if you search for the latest block, it will still show the data even with the error.
OK, I tried re-syncing, but I see the same problem !!! all suggestions are welcome, maybe I am missing something really small here... Could you post the log here? I don't remember where it is but it shouldn't be that hard to find.
|
|
|
Have you tried restarting insight or clearing its databases to resynce? That might help, otherwise, I don't know if what the problem is. Also, if you search for the latest block, it will still show the data even with the error.
|
|
|
I think they might be calculating everything on the fly so when you filter it, those balance calculations are based off of the data that it is showing, which may be why the balances are weird.
As for that one transaction which is included in the unconfirmed filter, I have no idea.
|
|
|
They are the same, I am starting it with npm start .
Edit: I get the net stats and block height, the problem is that insight doesn't submit latest blocks in the network
Do you start it with in the command because if you don't then it will default to testnet and it won't work properly.
|
|
|
Did you set the rpc user and password correctly both in the config file and in the environment variables when starting Insight?
I did set it in the config file at insight/node_modules/insight-bitcore-api/config/config.js is there any other config file that need to be changed beside that ? Make sure it the user and password are the same as the ones that you put into the coind config file. Also, what command are you using to start insight?
|
|
|
Because the data is still there and the same size. To download all of those blocks in those chunks is downloading the same amount of data from the p2p network. It won't be any faster and it all really depends on your network speed. The time for indexing all of those blocks is also the same because that is based on the cpu. Also, I remember someone mentioning that compression does not work well with Bitcoin blocks since there isn't much data that can be losslessly compressed.
|
|
|
Did you set the rpc user and password correctly both in the config file and in the environment variables when starting Insight?
|
|
|
Sorry everyone, but I don't have the site ready yet Life happened and I didn't have the time to set everything up. Fortunately, the code is almost done, I just need to add a few things for the production version which is slightly different from the github version (ads and ip waits). I think it will be done and the site will be up by Friday latest.
|
|
|
-snip log-
Are you sure that is the whole thing? I don't see any errors. He posted the correct part before but now, he has edited and replaced with irrelevant part. IIRC, there was some problem reading a block but I don't remember which one it was. Now that he reposted the whole thing, I see that the error is a database error. To fix the error, a reindex is required. On windows, right click the shortcut and select properties. Then in the box labeled Target, go to the end of the line, hit space, and add That will reindex the database which can take a few hours, but not as long as redownloading. That should fix the problem. None of your coins will be lost.
|
|
|
|