 Show Posts
|
|
Pages: [1] 2 »
|
|
The guides suggested are great and self explanatory for most ppl
I just fell into the usual normie traps; not being cmd savvy, not knowing I had to dl python to run rpcauth to get the output, not restarting tor and setting torrc as a txt file
So yeah if your like me and have tor running and cant find that onion address, get that torrc file sorted as above
|
|
|
|
How about this guide as a starting point to setup Tor on Windows: https://en.bitcoin.it/wiki/Setting_up_a_Tor_hidden_service#Windows --- I took only a quick look and didn't spot immediate problems, don't sell your car by my words.  I'm pretty sure the Tor project also has a decent tutorial or how-to available. Youtube likely has a ton of tutorials for Windows, too. my node already has tor enabled, I just dont seem to have an onion address anywhere to plug into specter to hook up to the node |
|
|
|
I have to mention that I set the 3 lines under " Control Port" instructed in the tutorial below, without it, the onion address wont show up: Try to follow either instruction number 2 or 3 from this tutorial: github.com/bitcoin/bitcoin/blob/master/doc/tor.mdIf you decided to follow number 3 instead, your onion address would be the one you set in -externalip. Appreciate the reply As I was telling Cricktor above I'm feeling this is a little over my head - I dont have a torrc file in my tor directory so I tried saving a torrc file there with those 3 lines. The node crashed so I deleted it again That tutorial is a hard follow. In number 2 'Cookie authentication' where is the CookieAuthFile and how do I enable read access? Number 3; I save HiddenServiceDir /var/lib/tor/bitcoin-service/
HiddenServicePort 8333 127.0.0.1:8334 as torrc file and run ./bitcoind -proxy=127.0.0.1:9050 -externalip=7zvj7a2imdgkdbg4f2dryd5rgtrn7upivr5eeij4cicjh65pooxeshid.onion -listen from what location? and how do I generate my onion address? |
|
|
|
You should pay attention to close your Bitcoin Core GUI gracefully via File menu and Quit, wait until it actually all closes.
noted I don't run Bitcoin Core in Windows, I run my Core in Linux and not with the GUI.
Yeah Im kinda regretting the decision to run this node on windows as I'm not at the linux level however most of the guides out there are linux based so prob would have been easier. As a novice a lot of these guides omit steps on the expectation that you should know..which I dont Your setup only allows connections via tor (same as mine) and all your peers have indeed only onion addresses. So, that part is working properly. What did you install for Tor? Maybe you can find there some log entries indicating the onion address of your node?
I'm not sure if the reason could be that your Core can't properly communicate via the torcontrol. A log entry that torcontrol thread started is in your debul.log. Check if you have your Tor properly configured for Windows environment (can't help here much, but there are certainly thread on the topic Tor setup on Windows in this forum, too).
All I did was copy that bitcoin.config file save and run. The node crashed so I tried looking for solutions. This guide https://miloserdov.org/?p=1839 alerted to the fact that I needed to install TOR as a service to keep it running. Soon as I did that and started bitcoin core I got oputbound running peers. I havent configured tor and I have no torrc file in the tor directory and have no idea what torcontrol is That's not what I wrote in my post:
bitcoin-cli.exe getnetworkinfo
Yeah sorry I assumed that was the executable for linux or something cuz the only exe I have in is bitcoin\bitcoin-qt I found bitcoin-cli in the daemon folder and this is what I got c:\Program Files\Bitcoin\daemon>bitcoin-cli.exe getnetworkinfo
error: Could not locate RPC credentials. No authentication cookie could be found, and RPC password is not set. See -rpcpassword and -stdinrpcpass. |
|
|
|
Have a look into the debug.log file (the standard location is in the data directory of Bitcoin Core which on Windows should be %APPDATA%\Bitcoin\). When the node starts the log entries start off with lines like: 2024-04-20T10:33:38Z Bitcoin Core version v26.0.0 (release build)
...
After some lines and ...
2024-04-20T11:06:52Z init message: Done loading
...
you might find a line like this near the above "init message: Done loading" entry 2024-04-20T11:06:52Z [tor] Got service ID <redacted to preserve privacy>, advertising service <redacted to preserve privacy>.onion:8333
You should see there the onion address of your node. You can also execute in a command line window bitcoin-cli.exe getnetworkinfo or getnetworkinfo in the console tab of the Bitcoin Core GUI window. The mostly last record of the above command's output for "localaddresses" also contains your local .onion address. Appreciate the reply sir but Ive tried all that. Here is my entire node start from debug 2024-04-29T06:46:08Z Bitcoin Core version v25.0.0 (release build)
2024-04-29T06:46:08Z InitParameterInteraction: parameter interaction: -proxy set -> setting -upnp=0
2024-04-29T06:46:08Z InitParameterInteraction: parameter interaction: -proxy set -> setting -natpmp=0
2024-04-29T06:46:08Z InitParameterInteraction: parameter interaction: -proxy set -> setting -discover=0
2024-04-29T06:46:08Z InitParameterInteraction: parameter interaction: -onlynet excludes IPv4 and IPv6 -> setting -dnsseed=0
2024-04-29T06:46:08Z Qt 5.15.5 (static), plugin=windows (static)
2024-04-29T06:46:08Z Static plugins:
2024-04-29T06:46:08Z QWindowsIntegrationPlugin, version 331520
2024-04-29T06:46:08Z QWindowsVistaStylePlugin, version 331520
2024-04-29T06:46:08Z Style: windowsvista / QWindowsVistaStyle
2024-04-29T06:46:08Z System: Windows 10 Version 2009, x86_64-little_endian-llp64
2024-04-29T06:46:08Z Screen: \\.\DISPLAY2 1280x720, pixel ratio=3.0
2024-04-29T06:46:08Z Using the 'x86_shani(1way,2way)' SHA256 implementation
2024-04-29T06:46:08Z Using RdSeed as an additional entropy source
2024-04-29T06:46:08Z Using RdRand as an additional entropy source
2024-04-29T06:46:08Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely…"
2024-04-29T06:46:09Z Default data directory C:\Users\Taconator3000\AppData\Roaming\Bitcoin
2024-04-29T06:46:09Z Using data directory D:\
2024-04-29T06:46:09Z Config file: D:\bitcoin.conf
2024-04-29T06:46:09Z Config file arg: disablewallet="0"
2024-04-29T06:46:09Z Config file arg: listen="1"
2024-04-29T06:46:09Z Config file arg: listenonion="1"
2024-04-29T06:46:09Z Config file arg: onion="127.0.0.1:9050"
2024-04-29T06:46:09Z Config file arg: onlynet="onion"
2024-04-29T06:46:09Z Config file arg: proxy="127.0.0.1:9050"
2024-04-29T06:46:09Z Config file arg: proxyrandomize="1"
2024-04-29T06:46:09Z Config file arg: rpcauth=****
2024-04-29T06:46:09Z Config file arg: rpcpassword=****
2024-04-29T06:46:09Z Config file arg: rpcport="8332"
2024-04-29T06:46:09Z Config file arg: rpcuser=****
2024-04-29T06:46:09Z Config file arg: server="1"
2024-04-29T06:46:09Z Setting file arg: dbcache = "4096"
2024-04-29T06:46:09Z Setting file arg: onion = "127.0.0.1:9050"
2024-04-29T06:46:09Z Setting file arg: par = "15"
2024-04-29T06:46:09Z Setting file arg: server = true
2024-04-29T06:46:09Z Using at most 125 automatic connections (2048 file descriptors available)
2024-04-29T06:46:09Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2024-04-29T06:46:09Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2024-04-29T06:46:09Z Script verification uses 14 additional threads
2024-04-29T06:46:09Z scheduler thread start
2024-04-29T06:46:09Z Binding RPC on address ::1 port 8332
2024-04-29T06:46:09Z Binding RPC on address 127.0.0.1 port 8332
2024-04-29T06:46:09Z [http] creating work queue of depth 16
2024-04-29T06:46:09Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
2024-04-29T06:46:09Z Using rpcauth authentication.
2024-04-29T06:46:09Z [http] starting 4 worker threads
2024-04-29T06:46:09Z Using wallet directory D:\
2024-04-29T06:46:09Z init message: Verifying wallet(s)…
2024-04-29T06:46:09Z Using /16 prefix for IP bucketing
2024-04-29T06:46:09Z init message: Loading P2P addresses…
2024-04-29T06:46:09Z Loaded 65238 addresses from peers.dat 156ms
2024-04-29T06:46:09Z init message: Loading banlist…
2024-04-29T06:46:09Z SetNetworkActive: true
2024-04-29T06:46:09Z Cache configuration:
2024-04-29T06:46:09Z * Using 2.0 MiB for block index database
2024-04-29T06:46:09Z * Using 8.0 MiB for chain state database
2024-04-29T06:46:09Z * Using 4086.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2024-04-29T06:46:09Z init message: Loading block index…
2024-04-29T06:46:09Z Assuming ancestors of block 000000000000000000035c3f0d31e71a5ee24c5aaf3354689f65bd7b07dee632 have valid signatures.
2024-04-29T06:46:09Z Setting nMinimumChainWork=000000000000000000000000000000000000000044a50fe819c39ad624021859
2024-04-29T06:46:09Z Opening LevelDB in D:\blocks\index
2024-04-29T06:46:09Z Opened LevelDB successfully
2024-04-29T06:46:09Z Using obfuscation key for D:\blocks\index: 0000000000000000
2024-04-29T06:46:13Z LoadBlockIndexDB: last block file = 4259
2024-04-29T06:46:13Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=26, size=41623023, heights=841308...841333, time=2024-04-29...2024-04-29)
2024-04-29T06:46:13Z Checking all blk files are present...
2024-04-29T06:48:10Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2024-04-29T06:48:10Z Opening LevelDB in D:\chainstate
2024-04-29T06:48:10Z Opened LevelDB successfully
2024-04-29T06:48:10Z Using obfuscation key for D:\chainstate: 51f7db2fd055050b
2024-04-29T06:48:10Z Loaded best chain: hashBestChain=000000000000000000018491979607466dd7e90253234970fe856324e1a1b97c height=841333 date=2024-04-29T06:28:43Z progress=0.999996
2024-04-29T06:48:10Z [snapshot] allocating all cache to the IBD chainstate
2024-04-29T06:48:10Z Opening LevelDB in D:\chainstate
2024-04-29T06:48:10Z Opened LevelDB successfully
2024-04-29T06:48:10Z Using obfuscation key for D:\chainstate: 51f7db2fd055050b
2024-04-29T06:48:10Z [Chainstate [ibd] @ height 841333 (000000000000000000018491979607466dd7e90253234970fe856324e1a1b97c)] resized coinsdb cache to 8.0 MiB
2024-04-29T06:48:10Z [Chainstate [ibd] @ height 841333 (000000000000000000018491979607466dd7e90253234970fe856324e1a1b97c)] resized coinstip cache to 4086.0 MiB
2024-04-29T06:48:10Z init message: Verifying blocks…
2024-04-29T06:48:10Z Verifying last 6 blocks at level 3
2024-04-29T06:48:10Z Verification progress: 0%
2024-04-29T06:48:11Z Verification progress: 16%
2024-04-29T06:48:11Z Verification progress: 33%
2024-04-29T06:48:12Z Verification progress: 50%
2024-04-29T06:48:12Z Verification progress: 66%
2024-04-29T06:48:12Z Verification progress: 83%
2024-04-29T06:48:13Z Verification progress: 99%
2024-04-29T06:48:13Z Verification: No coin database inconsistencies in last 6 blocks (16005 transactions)
2024-04-29T06:48:13Z block index 123741ms
2024-04-29T06:48:13Z Setting NODE_NETWORK on non-prune mode
2024-04-29T06:48:13Z block tree size = 841334
2024-04-29T06:48:13Z nBestHeight = 841333
2024-04-29T06:48:13Z loadblk thread start
2024-04-29T06:48:13Z torcontrol thread start
2024-04-29T06:48:13Z Leaving InitialBlockDownload (latching to false)
2024-04-29T06:48:13Z Bound to 127.0.0.1:8334
2024-04-29T06:48:13Z Bound to [::]:8333
2024-04-29T06:48:13Z Bound to 0.0.0.0:8333
2024-04-29T06:48:13Z Loaded 2 addresses from "anchors.dat"
2024-04-29T06:48:13Z 2 block-relay-only anchors will be tried for connections.
2024-04-29T06:48:13Z init message: Starting network threads…
2024-04-29T06:48:13Z net thread start
2024-04-29T06:48:13Z DNS seeding disabled
2024-04-29T06:48:13Z addcon thread start
2024-04-29T06:48:13Z opencon thread start
2024-04-29T06:48:13Z msghand thread start
2024-04-29T06:48:13Z init message: Done loading
2024-04-29T06:48:13Z GUI: Platform customization: "windows"
2024-04-29T06:48:25Z New outbound peer connected: version: 70016, blocks=841334, peer=0 (block-relay-only)
2024-04-29T06:48:28Z Saw new header hash=000000000000000000032e1cecf170a76757b9bad0c114255dde54839f4e890d height=841334
getnetworkinfo in console 
{
"version": 250000,
"subversion": "/Satoshi:25.0.0/",
"protocolversion": 70016,
"localservices": "0000000000000409",
"localservicesnames": [
"NETWORK",
"WITNESS",
"NETWORK_LIMITED"
],
"localrelay": true,
"timeoffset": -1,
"networkactive": true,
"connections": 10,
"connections_in": 0,
"connections_out": 10,
"networks": [
{
"name": "ipv4",
"limited": true,
"reachable": false,
"proxy": "127.0.0.1:9050",
"proxy_randomize_credentials": true
},
{
"name": "ipv6",
"limited": true,
"reachable": false,
"proxy": "127.0.0.1:9050",
"proxy_randomize_credentials": true
},
{
"name": "onion",
"limited": false,
"reachable": true,
"proxy": "127.0.0.1:9050",
"proxy_randomize_credentials": true
},
{
"name": "i2p",
"limited": true,
"reachable": false,
"proxy": "",
"proxy_randomize_credentials": false
},
{
"name": "cjdns",
"limited": true,
"reachable": false,
"proxy": "127.0.0.1:9050",
"proxy_randomize_credentials": true
}
],
"relayfee": 0.00001000,
"incrementalfee": 0.00001000,
"localaddresses": [
],
"warnings": ""
}
I tried bitcoin-qt.exe getnetworkinfo in command prompt but that only started bitcoin core? Here is my peers window showing onion outbound connections  Anyone got any ideas why my tor hidden service is really hidden?   |
|
|
|
|
Noob here, running full node on windows regrettably and just managed to run it through Tor hidden service albeit 0 incoming connections 10 outbound
Problem is I have no router access so I wanted to connect to my node via specter however I cant find it for the life of me as all info online is for different linux distros
|
|
|
|
|
(a) mchlnmstr
(b) 37fZxfFHsxnHdAcaYGsys41YoD8aqU8Xhg
(c) carbon7dna
(d) VALIDATE.
|
|
|
|
|
The thing that I love about this project and why I invested in the ICO is that loyalty is a great use case for crypto. When I studied marketing I remember reading about how disjointed the loyalty industry is currently with high costs to merchants and the yearly billions of unclaimed loyalty points. Hopefully launch goes as planned and if the system is setup so that merchant adoption is seamless (sounds as if it will be) and it starts to catch on with customers, adoption could snowball. Small team but after the setbacks I believe Rob has the right stuff to deliver
|
|
|
|
|
I sent eth from an unsupported wallet (exodus) will eos make it possible for me to claim my tokens at some stage?
|
|
|
|
|
Hi, I had my AMPS stored in Electrum wallet. I withdrew all my bitcoin out of it to get my Bcash however it also took all my amps with the BItcoin...is there a way to recover my amps or are they lost?
Thanks in advance
|
|
|
|
|
anyone know whats up with the 1st slack channel? I cant seem to locate the #General channel, is it still there?
|
|
|
|
when can I get my incent bonus for ETT?
You already asked and got the answer on Slack. Why ask again here? I asked incent team for eta of incent bonus for ETT on slack And received no response. Did the ama even happen? Incent seems to be in dark hours...no communication, no monthly report (who wants to hear more of this debacle I guess) ...so when ama? |
|
|
|
IT is always the same: nobody wants to take any risks for investments, but everybody wants to get rich in a few days... Testify!  Yeah everyone wants cheaper tokens than presale with moon launch |
|
|
|
This ICO is very quiet. Won't they do any effort on marketing here?
How many dollars have been raised so far?
Outside of the $4 million from private contributions, about 320 BTC have thus far been raised. The ICO may currently be a bit quiet but the tech is anything but... Also, the price between different stages is very different. For angel investors, the price is about 2 dollars (and further they will get more tokens freely if they hold the UIA). For private contributions, the price is 4dollars (1mil tokens for 4mil dollars). For us (public), the price is at least 5dollars. So .... you know. Every past token is a UIA lol I was very excited about this ICO, was plan to buy big but decide to research and read the whole thread for few hours to finish. But lol, this is quite MISLEADING for new buyers. They think the past ico was sold for 2 and 3 dollars and now its only 5$. So its possible to buy. But in reality the price already pumped up to 41 dollar when their OWN exchange halted. I think they had it all planned to pumped to price up before freeze the exchange so they can profit from the 2nd ico for the public. If you read the whole thread people were suprise the price went to $41 and right after it get freeze. Someone bought over 60 btc at the end. Dont you guys think one of the members could just pump the price up before freezing and strike millions with 2nd ICO? Yes thats possible. All the 1 million token are increase 10x. So there will be 10million tokens. But they say maximum 9million. I wonder where the 1 million tokens went since the tokens increase 10x So previous price of 1 token on the exchange was $41 Since its all User-Issued Assets (UIA) the whole 1million token its change 10x to 10million, so the price will be in reality 1 token will be 10 new tokens, each of $4.10 but i guess they upgrade it to $5 they need to make money from the end pump at least. I meant, which idiot will buy 60 btc when the btc price was $600 and not complain here why the exchange is freezing. He bought 3k coins means with the 2nd ICO he will have 30k new coins. So conclusion: YOU DONT BUY FOR $5 per token but in reality $50 per token you spent `hours` doing research yet you didnt read the peerplays bulletin? Your ramblings make little sense, here let me clear a few things up for you: the part where it says in plain english - 200,000 uai`s were sold in presale. UAI holders got the choice to sell their tokens for $48 or whatever or get 10x PPY tokens (10x200,000 is 2 million showing in the `seed crowdfund` distribution table) I dunno where ur getting 10x10 million from, you clearly do not understand what you`re blabbering about So i dont really get what you`re complaining about, Im sure if you prefer to pay $48 instead of $5 it could be arranged? |
|
|
|
|
we hit ico price already and there are still knob jockeys here pleading for listings to flip incent? These arbitrage holders are the scurge to the community
|
|
|
|
As i am a investor from the "first hour" and bought a lot of more between price range from 5000-3000 satoshis i am interested in how, beside the business itsself, you are in contact with bigger exchanges to make Incent more "pupular" to a broader audience. Nothing against cryptopia, its the beginning, but even there the daily volumne is about just 10 BTC, the spreads for buying and selling are way too big (right about now its nearly 30%!!!). Maybe another try with BITTREX would not the worst idea of all.
We have been in contact with a bigger exchange - everything should be ready to go, so not sure what the delay is. Other than that, we'll be bringing volume to the exchanges. That comes under the heading 'by the business itself', I suppose, but the point is that having exchanges without adoption and external demand is the tail wagging the dog (even if it's the norm in crypto). Actually early investors want profitable exit in current trend so looking over the current is very terrible when we already lost a lot of amount. Actually as an early investor I was under no such delusions of cashing out a 10x profit any time before incent went to market. To believe so would indicate that u really shouldnt be trusting yourself with your bitcoin private keys...surely u could even entrust ur wife to make more realistic sound financial decisions on ur behalf? Ps. No losses have been made till you cash out |
|
|
|
peerplays is not charging you guys 5.00 a coin its 50 dollars on this 2nd round of funding. So what they are doing is 10xing everyones holdings who bought on the first crowd fund who paid 2 to 3.00 a coin. The people paying 5.00 a coin will not get a 10x on the 2nd crowd fund of the coin. So the president i talked to confirmed it. So basically if you bought in the first ico you get a nice deal the people who are buying now are paying like 50 bucks a coin because you wont get a 10x inflation like the first round. So this is imo a rip off for the 2nd round buyers. He thinks its ok to boost the ico pric eto around 50 bucks cause they closed it at 41 on market cap that has nothing to do with a ico price. They are going to have 10 millions and who knows who these 4 million dollar private investors are they can easily flood the market with peer plays and destroy the price of it. Maybe they hold and it stays around 5.00 but I doubt it. This 5.00 price is a rip off. Its double the price of the first ico and your not getting a 10x inflation like everyone else ( including the private investors) from my understanding.
peerplays uia's were traded at $41 before they were locked at 23rd of december. so if you are calculating a little bit, it is a quite fair deal that is offered to the new investors. remember: the tokens are locked since december and can't be traded since the end of may. nearly half a year our money is blocked and we are taking the risk that they are not running away with our money... so tell me, what risks are YOU taking, if you are investing now, at a time when the peersplays blockchain has been developed and ready to take off? That has nothing to do with new investors. If it got halted that is not new investors problem. So if it got halted at 41 they should be 4.10 cents if they want to follow the market cap. Not 5.00 and tell people they are paying for a 41 million market cap. The people buying into this ico are being over charged. An ico is about getting it cheaper before it hits the market. Not the market price when it was really high. So if there is no lock out period for the 4 million from private investors ( who remain anonymous no proof of other investors) they can flood the market with peerplays and sell all of their shares and destroy the price and buy back at a lower price. I just don't think they will get many more investors in this ico. I been wrong before but this is very fishy to me. But gl with it I do hope it works out for everyone as I have heard the co founder is well known and respected person in the crypto community. So we will see but I am just going to wait for it to hit the market and expect the 4 million dollar investors to sell off and I can get it much cheaper. I do like the idea of it. And if I am wrong I guess I will miss the boat on this one. I beleive ur assuming a little too much on that, I mean normally ico's offer up special deals to bulk investors. That is if their buying structure is tiered, there would be no advantage to them to buy bag fulls at the price the average joe buys in right? Doubt any of these strategic investors paid anywhere near 5 bucks |
|
|
|
Last year during our presale it went exactly the same way only 10x less than what we are seeing today. Then we were raising $500k and was finished inside of almost 6 weeks. Now we are raising $5m and we have until May 14th to get there. Things are looking good from where we are sitting and on par with last year.. which was successful... there is indeed more news coming. Im spending way too much btc on this, its a no brainer. Hoping it will get out of tier 1 soon so I cut it out  I only noticed this projet when I opened a openledger account and price was already $14 for the pre sale tokens by then so im just thrilled I wasnt too late overall. This project seems to fly under the radar but it has huge potential Once it goes live and punters start catching on it will spread like wildfire...by then it will be too late to get on I believe last year they had 1 million coins now they have 6 million.... So that cuts into the price a bit. Yeah 6 million is still a comparitively low supply |
|
|
|
When I understand correctly, then conditional payments are like smart contracts, right? It is just another name for it isn't it?
Conditional payments is an application based on smart contracts. I want to ask How can I get if my bitcoin balance existing in the wallet for 1btc how to calculate the distribution amount byteball do we get? The distribution rules: BTC to bytes: 1 BTC of proven balance gives you 62.5 MB (0.0625 GB) BTC to blackbytes: 1 BTC of proven balance gives you 2.1111 * 62.5 million blackbytes (money supply of blackbytes is 2.1111 times more than that of bytes) Bytes to bytes: 1 byte on any Byteball address gives you 0.1 new bytes Bytes to blackbytes: 1 byte on linked Byteball address gives you 0.21111 blackbytes so do we have to do anything to get the 0.1 per 1 byte on Byteball addresses or do all byteball addresses get credited automatically? |
|
|
|
|
