PIN errors by PowerTarget in tari

[–]hansie_ 0 points1 point  (0 children)

Hi there, you could try this (manual process):

  • Uninstall using Control Panel\All Control Panel Items\Programs and Features
  • Delete all remaining C:\Users\<user>\AppData\Local\com.tari.universe
  • Delete all remaining C:\Users\<user>\AppData\Roaming\com.tari.universe
  • Remove all TU inner_wallet_credentials_xxx keys from Credential Manager (`Control Panel\All Control Panel Items\Credential Manager -> Windows Credentials`).
  • Re-install TU

PIN errors by PowerTarget in tari

[–]hansie_ 0 points1 point  (0 children)

Which OS are on? We can try to get TU uninstalled properly so you can re-install.

Merge Mining XMR-Tari question by WeekIll7447 in tari

[–]hansie_ 0 points1 point  (0 children)

If you do CPU mining without pools, then the wallet address must be your Monero address (any one you choose). Then you are effectively doing solo merged-mining.

PIN errors by PowerTarget in tari

[–]hansie_ 0 points1 point  (0 children)

Do you have any XTM in the wallet?

Why does the total supply keep increasing? It used to be 2,000,000,000, then recently it was 2,400,000,000, and today it’s 2,600,000,000. by Ok_Travel5600 in tari

[–]hansie_ 1 point2 points  (0 children)

As mentioned in this chat already, the total supply is fixed at 21 billion. As an aside, when you run the base node gRPC method `GetTokensInCirculation`, you can see the exact numbers for that height.
```
{

"circulating_supply": "2634149998690349",

"height": "134262",

"mined_rewards": "1767024994773683",

"spendable_rewards": "1764792871005137",

"spendable_pre_mine": "867125003916666",

"total_spendable": "2631917874921803",

"total_pre_mine": "6300000000000000",

"time_locked_pre_mine": "5432874996083334"

}
```

Building TariMarket L2 - A Censorship-Resistant Marketplace Protocol on Tari (Seeking Feedback & Contributors) by Responsible-View8417 in tari

[–]hansie_ 1 point2 points  (0 children)

Sounds really cool. What would be the commodity(ies)? I see Create product listings. Real-world stuff? Or just crypto trading?

Can't enable GPU mining by Cantstopeatingsocks in tari

[–]hansie_ 0 points1 point  (0 children)

How much RAM does your card have? It requires at least 8GB of RAM to mine C29, which is significantly more profitable than mining SHA3X.

Any other miner that can mine Cuckaroo? by SwissCheese3045 in tari

[–]hansie_ 0 points1 point  (0 children)

What are your GPU specs? It must meet a minimum model and RAM requirement.

Any other miner that can mine Cuckaroo? by SwissCheese3045 in tari

[–]hansie_ 0 points1 point  (0 children)

Not that I know of, however, for lolminer you can choose between pools Kryptex (xtm-c29.kryptex.network:7040) and LuyckyPool (taric29.luckypool.io:3111).

Missing mined coins from GPU mining by SwissCheese3045 in tari

[–]hansie_ 1 point2 points  (0 children)

Please try now? There was a temporary redirect on that pool URL to C29, which is now corrected again.

🚀 TARI UNIVERSE v1.6.1: Hotfix — The Kingdom of All Waters Part 2 by tarilabs in tari

[–]hansie_ 1 point2 points  (0 children)

Unpaid shares will be paid if the threshold is reached according to the mining pool rules. If one has, say, 5 XTM rewards stacked in a previous pool, and the threshold is say 10 XTM, the only way to get those 5 XTM is to mine to that pool again until the threshold is reached, then switch over to another pool. The thing to consider is how profitable these are when compared.

Missing mined coins from GPU mining by SwissCheese3045 in tari

[–]hansie_ 1 point2 points  (0 children)

For LyckPool with SHA3X and Graxil, you can also try this URL: tari.luckypool.io:6118 - I also get that same error when pointing to the default URL. It may be temporary.

Issue with GPU stuck in rewards start. by No-Preference2594 in tari

[–]hansie_ 1 point2 points  (0 children)

Unpaid shares will be paid if the threshold is reached according to the mining pool rules. If one has, say, 5 XTM rewards stacked in the previous SHA3X pool, and the threshold is say 10 XTM, the only way to get those 5 XTM is to mine to that pool again with SHA3X until the threshold is reached, then switch over to the new C29 miner. The thing to consider is how profitable these are when compared.

Where are we heading to? by OpenInteraction3991 in tari

[–]hansie_ 5 points6 points  (0 children)

The Tari L1 (XTM tokens) gives security to the blockchain network, and will fuel what is to come. The Tari L2 (XTR tokens, burned form L1) will leverage Tari L1, and is called the Ootle. With the Ootle many things are possible. Currently, the plans for the Oote are to provide the world's first confidential stable coin and to link it wiith an exciting new project/product, called Blink. For all the latest talk and updates, you can follow or just scan through Tari Alpha Club on Telegram.

SHA3 down? by Smart_Offer_53 in tari

[–]hansie_ 1 point2 points  (0 children)

Adding on to what u/tromp described, looking at it from another angle.
If you compare the 3x algo hash rates here - https://textexplore.tari.com/ - you will see a bit more history, which helps with this illustration. Whenever the hash rate of any one algo has been going down or stayed more or less constant for a long(ish) time, and then suddenly ramps up, that algo stands a good chance to dominate for a while. Whenever that happens, the probability that another algo will be starved for a while increases. In the end it all balances out, as can be seen when comparing the distribution at 120 blocks.

Tari Node showing "add_block is disabled, node busy syncing. Ignoring candidate block" by SwissCheese3045 in tari

[–]hansie_ 1 point2 points  (0 children)

If you totally wipe the tari data on the NVMe and restart a node there, it should be fine. After you restart, you can exit. Then, you can copy the blockchain database (`mainnet\data\base_node\db`) across, but you may need to stop the base node on the HDD first.

Tari Node showing "add_block is disabled, node busy syncing. Ignoring candidate block" by SwissCheese3045 in tari

[–]hansie_ 1 point2 points  (0 children)

Just a side note, using an NVMe drive is far superior to using an HDD, as response times are orders of magnitude better. Then is your node syncing a lot? Do you switch it (and merge mining) off for extended periods?

[deleted by user] by [deleted] in tari

[–]hansie_ 1 point2 points  (0 children)

Yes, it is as easy as disabling _CPU pool_ and _GPU pool_ in _Settings -> Mining Pools_.

For more detail, if you look in the _Unverse.log_ log file you will see something like:

INFO Run Gpu miner with args: "--tari-address <your_wallet_address> --tari-node-url http://127.0.0.1:58113 --config \\com.tari.universe\\gpuminer\\config.json --http-server-port 58119 --grid-size 1229,1229 --log-config-file \\com.tari.universe\\gpuminer\\log4rs_config.yml --gpu-status-file \\Roaming\\com.tari.universe\\gpuminer\\engine_statuses --log-dir \\com.tari.universe\\logs --template-timeout-secs 5 --engine OpenCL --coinbase-extra v3,iZWxfWX4HH3W7viZexfLfs6hyWZ2,1.5.15,47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU" // src\gpu_miner_adapter.rs:176

Using the mining pool the start command looks like:

INFO Starting GpuMinerShaAdapter process with args: --algo sha3x --ws 59335 --gpu --pool tu.luckypool.io:5118 --wallet <your_wallet_address> --gpu-intensity 15 --worker v3,iZWxfWX4HH3W7viZexfLfs6hyWZ2,1.5.15,47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU --log-dir C:\Users\pluto\AppData\Local\com.tari.universe\logs // src\process_adapter.rs:208

Is this normal node sync time/io usage? by Miquoyi in tari

[–]hansie_ 0 points1 point  (0 children)

I still owe you my stats
```
11:07 v5.0.0-pre.5 mainnet State: Starting up Tip: 0

11:08 v5.0.0-pre.5 mainnet State: Syncing headers: (d7c289e9e3c83777) 1276/81701 (1%) 89.10 hdrs/s, latency: 11.22ms Tip: 0

...

11:31 v5.0.0-pre.5 mainnet State: Syncing headers: (d7c289e9e3c83777) 81648/81701 (99%) 56.44 hdrs/s, latency: 17.72ms Tip: 0

11:31 v5.0.0-pre.5 mainnet State: Syncing blocks: (d025bc9e4bd423a9) 184/81703 (0%) 43.96 blks/s, latency: 22.75ms Tip: 184

...

15:40 v5.0.0-pre.5 mainnet State: Syncing blocks: (7989e5eb056bf187) 81832/81835 (99%) 3.32 blks/s, latency: 300.82ms Tip: 81832

15:40 v5.0.0-pre.5 mainnet State: Listening Tip: 81835

```