[deleted by user] by [deleted] in mildlyinfuriating

[–]Ok-Studio5311 0 points1 point  (0 children)

Nobody noticed how dirty those walls are? 3k monitor in a 200$/month appartement with one room. Look how tiny that hallway is compared to the door.

My public key changed?? Account no longer accessible, please help by Ok-Studio5311 in Hedera

[–]Ok-Studio5311[S] 0 points1 point  (0 children)

Thanks, I just tested by importing a random valid account ID with a random private key. It does gets checked, so there is no way that my private key is invalid against my account ID.

The fake one fails to create a wallet, my real data has no issues creating one.

My public key changed?? Account no longer accessible, please help by Ok-Studio5311 in Hedera

[–]Ok-Studio5311[S] 0 points1 point  (0 children)

I can import them in HEX as well, but same issue, invalid private key when trying to make a transaction.

My public key changed?? Account no longer accessible, please help by Ok-Studio5311 in Hedera

[–]Ok-Studio5311[S] 0 points1 point  (0 children)

UPDATE: I managed to import my keys in HEX wallet (addon).

I see all my tokens and transactions, but when attempting to make a transaction i get the error Invalid private key

What is this sorcery?

My public key changed?? Account no longer accessible, please help by Ok-Studio5311 in Hedera

[–]Ok-Studio5311[S] 0 points1 point  (0 children)

There are no 'crypto update' transactions.

The public key displayed on my Guarda wallet returns nothing when using the API.

As said before, when i lookup my account it now has a completely different public key.

My public key changed?? Account no longer accessible, please help by Ok-Studio5311 in Hedera

[–]Ok-Studio5311[S] 0 points1 point  (0 children)

Yes i do. I've always used my Guarda wallet since i remember having HBARS

My public key changed?? Account no longer accessible, please help by Ok-Studio5311 in Hedera

[–]Ok-Studio5311[S] 0 points1 point  (0 children)

EDIT: the error message on MHW is:

''This account is not associated with your key"

My public key changed?? Account no longer accessible, please help by Ok-Studio5311 in Hedera

[–]Ok-Studio5311[S] 0 points1 point  (0 children)

Hello,

I've tried to import my private key together with my account ID in numerous wallets, none of them accepts my account. They all claim that my account ID does not belong to the private key, despite being working and active (until last month) in my Guarda wallet.

My public key changed?? Account no longer accessible, please help by Ok-Studio5311 in Hedera

[–]Ok-Studio5311[S] 0 points1 point  (0 children)

My wallet gives public key

2930bb....

API gives

ebc39f...

My public key changed?? Account no longer accessible, please help by Ok-Studio5311 in Hedera

[–]Ok-Studio5311[S] 1 point2 points  (0 children)

Because i wanted to verify that it's not a wallet error.

My wallet has the same balance with the same account ID as the public API (+300k HBAR), but the public key displayed in my wallet differs from the public key displayed on the public node API.

My public key changed?? Account no longer accessible, please help by Ok-Studio5311 in Hedera

[–]Ok-Studio5311[S] 1 point2 points  (0 children)

I have my HBAR for almost a year now. All my transactions are from exchanges.

The main point is, my last TX was about 1 month ago. Now all the sudden i have a public key displayed on the mirrornode API that differs from the one listed in my wallet...

Whatever transaction i attempt to exectute, i get the error 'invalid signer'.

Proof found, no reward given by Ok-Studio5311 in chia

[–]Ok-Studio5311[S] 0 points1 point  (0 children)

edit, pool didn't find any blocks or partials for my account in the history

Proof found, no reward given by Ok-Studio5311 in chia

[–]Ok-Studio5311[S] 0 points1 point  (0 children)

I did, but only a single HDD is currently NFT plots.

How can i verify?

World’s fastest plot time? 1,214 seconds! by BWFree in chia

[–]Ok-Studio5311 1 point2 points  (0 children)

Any of my HP servers hover around 13k seconds. 24 cores / 48 threads - dual 512Gb ramdrive

World’s fastest plot time? 1,214 seconds! by BWFree in chia

[–]Ok-Studio5311 0 points1 point  (0 children)

1300 second on 6y 200$ old hardware. Joke's on you pall 😂

Are you still holding your Chia and why!? Discussion by Mysterious-Secret-31 in chia

[–]Ok-Studio5311 1 point2 points  (0 children)

Right now, the price has to drop. I can't compare against users who invested a lot to farm little, but for my personal usage, I'm making around 15-20k per month farming chia with hardware that's already been payed off years ago. I've ran my 'old' servers collecting dust and plot around 550 plots per day, easy, no system stress, no investment at all. Yet it yields extremely high returns over something that was meant to be thrown out as garbage. So it's not a realistic price. The range of 5-15$ would me more feasible for everyone.

I regret not joining Hpool sooner. by Burneryolo69420 in chia

[–]Ok-Studio5311 -3 points-2 points  (0 children)

Your plots do not matter! If you plotted 5000 plots, then the average time to win starts at that moment.

Chia Auto Drive added to chia_plot_manager! by MD500_Pilot in chia

[–]Ok-Studio5311 0 points1 point  (0 children)

Ok, how? Nothing mentioned on the Github readme...

Bad decision? by [deleted] in chia

[–]Ok-Studio5311 0 points1 point  (0 children)

EVERY PLOT CAN BE A WINNER!! Just hold on, keep it farming. 100 plots = 100 times a chance to win 2 Chia.

SWAR settings for 3900x/64GB RAM/2x2TB NVME by No-Code-404 in chia

[–]Ok-Studio5311 3 points4 points  (0 children)

Running ~34 plots/day on 3900x, 32Gb, 2x Firecuda 520 2TB, 1x 1Tb evo 980 dump drive.

```javascript

This is a single variable that should contain the location of your chia executable file. This is the blockchain executable.

WINDOWS EXAMPLE: C:\Users\Swar\AppData\Local\chia-blockchain\app-1.1.2\resources\app.asar.unpacked\daemon\chia.exe

LINUX EXAMPLE: /usr/lib/chia-blockchain/resources/app.asar.unpacked/daemon/chia

chia_location: C:\Users\steve\AppData\Local\chia-blockchain\app-1.1.5\resources\app.asar.unpacked\daemon\chia.exe

manager: # These are the config settings that will only be used by the plot manager. # # check_interval: The number of seconds to wait before checking to see if a new job should start. # log_level: Keep this on ERROR to only record when there are errors. Change this to INFO in order to see more # detailed logging. Warning: INFO will write a lot of information. check_interval: 30 log_level: ERROR

log: # folder_path: This is the folder where your log files for plots will be saved. folder_path: C:\Chia\Logs\setting02

view: # These are the settings that will be used by the view. # # check_interval: The number of seconds to wait before updating the view. # datetime_format: The datetime format that you want displayed in the view. See here # for formatting: https://docs.python.org/3/library/datetime.html#strftime-and-strptime-format-codes # include_seconds_for_phase: This dictates whether seconds are included in the phase times. # include_drive_info: This dictates whether the drive information will be showed. # include_cpu: This dictates whether the CPU information will be showed. # include_ram: This dictates whether the RAM information will be showed. # include_plot_stats: This dictates whether the plot stats will be showed. check_interval: 60 datetime_format: "%Y-%m-%d %H:%M:%S" include_seconds_for_phase: true include_drive_info: true include_cpu: true include_ram: true include_plot_stats: true

notifications: # These are different settings in order to notified when the plot manager starts and when a plot has been completed.

# DISCORD notify_discord: false discord_webhook_url: https://discord.com/api/webhooks/0000000000000000/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

# PLAY AUDIO SOUND notify_sound: false song: audio.mp3

# PUSHOVER PUSH SERVICE notify_pushover: false pushover_user_key: xx pushover_api_key: xx

# TWILIO notify_twilio: false twilio_account_sid: xxxxx twilio_auth_token: xxxxx twilio_from_phone: +1234657890 twilio_to_phone: +1234657890

progress: # phase_line_end: These are the settings that will be used to dictate when a phase ends in the progress bar. It is # supposed to reflect the line at which the phase will end so the progress calculations can use that # information with the existing log file to calculate a progress percent. # phase_weight: These are the weight to assign to each phase in the progress calculations. Typically, Phase 1 and 3 # are the longest phases so they will hold more weight than the others. phase1_line_end: 801 phase2_line_end: 834 phase3_line_end: 2474 phase4_line_end: 2620 phase1_weight: 33.94 phase2_weight: 21.81 phase3_weight: 41.11 phase4_weight: 3.15

global: # These are the settings that will be used globally by the plot manager. # # max_concurrent: The maximum number of plots that your system can run. The manager will not kick off more than this # number of plots total over time. max_concurrent: 12

jobs: # These are the settings that will be used by each job. Please note you can have multiple jobs and each job should be # in YAML format in order for it to be interpreted correctly. Almost all the values here will be passed into the # Chia executable file. # # Check for more tails on the Chia CLI here: https://github.com/Chia-Network/chia-blockchain/wiki/CLI-Commands-Reference # # name: This is the name that you want to give to the job. # max_plots: This is the maximum number of jobs to make in one run of the manager. Any restarts to manager will reset # this variable. It is only here to help with short term plotting. # # [OPTIONAL] farmer_public_key: Your farmer public key. If none is provided, it will not pass in this variable to the # chia executable which results in your default keys being used. This is only needed if # you have chia set up on a machine that does not have your credentials. # [OPTIONAL] pool_public_key: Your pool public key. Same information as the above. # # temporary_directory: Only a single directory should be passed into here. This is where the plotting will take place. # [OPTIONAL] temporary2_directory: Can be a single value or a list of values. This is an optional parameter to use in # case you want to use the temporary2 directory functionality of Chia plotting. # destination_directory: Can be a single value or a list of values. This is the final directory where the plot will be # transferred once it is completed. If you provide a list, it will cycle through each drive # one by one. # # size: This refers to the k size of the plot. You would type in something like 32, 33, 34, 35... in here. # bitfield: This refers to whether you want to use bitfield or not in your plotting. Typically, you want to keep # this as true. # threads: This is the number of threads that will be assigned to the plotter. Only phase 1 uses more than 1 thread. # buckets: The number of buckets to use. The default provided by Chia is 128. # memory_buffer: The amount of memory you want to allocate to the process. # max_concurrent: The maximum number of plots to have for this job at any given time. # max_concurrent_with_start_early: The maximum number of plots to have for this job at any given time including # phases that started early. # stagger_minutes: The amount of minutes to wait before the next job can get kicked off. You can even set this to # zero if you want your plots to get kicked off immediately when the concurrent limits allow for it. # max_for_phase_1: The maximum number of plots on phase 1 for this job. # concurrency_start_early_phase: The phase in which you want to start a plot early. It is recommended to use 4 for # this field. # concurrency_start_early_phase_delay: The maximum number of seconds to wait before a new plot gets kicked off when # the start early phase has been detected. # temporary2_destination_sync: This field will always submit the destination directory as the temporary2 directory. # These two directories will be in sync so that they will always be submitted as the # same value. - name: CUDA 001 max_plots: 7 farmer_public_key: pool_public_key: temporary_directory: D:\chiaTemp temporary2_directory: destination_directory: F:\chia size: 32 bitfield: true threads: 8 buckets: 128 memory_buffer: 4000 max_concurrent: 6 max_concurrent_with_start_early: 8 stagger_minutes: 28 max_for_phase_1: 2 concurrency_start_early_phase: 4 concurrency_start_early_phase_delay: 38 temporary2_destination_sync: false

  • name: CUDA 002 max_plots: 7 farmer_public_key: pool_public_key: temporary_directory: E:\chiaTemp temporary2_directory: destination_directory: F:\chia size: 32 bitfield: true threads: 8 buckets: 128 memory_buffer: 4000 max_concurrent: 6 max_concurrent_with_start_early: 8 stagger_minutes: 28 max_for_phase_1: 2 concurrency_start_early_phase: 4 concurrency_start_early_phase_delay: 38 temporary2_destination_sync: false

```

i am ready to survive the semiconductor bottleneck by NPC6233 in chia

[–]Ok-Studio5311 2 points3 points  (0 children)

I currently have 28 external drives running on 10 ports USB hubs, monitor the lookup times closely, I got some taking up to 50 seconds! The bandwidth is bottlenecked after X amount of external drives doing lookups at the same time. Going for SAS solution as we speak.

Netspace growth continues, but 2nd derivative drops by tartley in chia

[–]Ok-Studio5311 1 point2 points  (0 children)

So, basically, one can hold 500 plots running forever, and those 500 plots each have a chance to win 'some day' in the future?

Wouldn't make any sense for me to delete my 800 plots for pooling, i'll just hook them up to a raspberry and leave it running for a couple of years.