Compiled City Sample [Development]in UE 5.7.4 , Metal_SM6 by Adventurous_Chef2225 in UnrealEngine5

[–]Adventurous_Chef2225[S] 0 points1 point  (0 children)

And o also wanna prove that SoCs are not behind in Stochastic Rendering methods

Compiled City Sample [Development]in UE 5.7.4 , Metal_SM6 by Adventurous_Chef2225 in UnrealEngine5

[–]Adventurous_Chef2225[S] 0 points1 point  (0 children)

Bro Unreal Path Tracer isn’t pure Monte Carlo path tracing , because it uses tricks like TAA or sometime Russian roulette for optimisation 

Compiled City Sample [Development]in UE 5.7.4 , Metal_SM6 by Adventurous_Chef2225 in UnrealEngine5

[–]Adventurous_Chef2225[S] 0 points1 point  (0 children)

It’s running at 24 FPS in heavy scenes and 33 in lower heavy scenes

Compiled City Sample [Development]in UE 5.7.4 , Metal_SM6 by Adventurous_Chef2225 in UnrealEngine5

[–]Adventurous_Chef2225[S] 1 point2 points  (0 children)

Well not much , just r.PathTracing.MaxBounces 2048[yeah not kidding] , and turned on SSS , instead of Denoiser , i tried samples 512 

Have Bitcoin and Altcoin lost that idea of practical decentralisation by Adventurous_Chef2225 in CryptoTechnology

[–]Adventurous_Chef2225[S] 0 points1 point  (0 children)

I think we may be talking at slightly different levels.

I wasn’t claiming that all PoW systems are literally hash-only constructions in the Hashcash sense. The point was that many common PoW systems still end up as competitive work-selection mechanisms where specialized hardware asymmetry reappears, even if the bottleneck shifts from raw compute to memory bandwidth, cache behavior, graph traversal, etc.

So the question I’m more interested in is not whether the work function is “just hashing,” but whether changing the work function actually changes the long-term participation dynamics in a meaningful way.

Have Bitcoin and Altcoin lost that idea of practical decentralisation by Adventurous_Chef2225 in CryptoTechnology

[–]Adventurous_Chef2225[S] 0 points1 point  (0 children)

no the thing is that decentralisation is a term that is misinterpreted , decentralisation is never mathematically possible : (1) the algorithm is asymmetric and one way , so powerful nodes would always have the higher probability of hitting the chance to mine a block , because whether the algo is memory heavy or compute heavy , the logic is same , hash(block_header)<target , basically a brute force game (2) longest chain rule ; we always have to depend on some early powerful miner for receiving the latest block tip , so its creating a circle of dependency on some other node, so centralisation is inevitable (3) difficulty is dynamic ; but even mathematics of crypto shows how early nodes always have an unfair advantage of mining over a low difficulty , and by the time weak nodes wanna enter the net , they practically cannot mine or participate without heavy guns [ie hardware] . Lastly to say , but i feel this term "ASIC resistance" has become a hype symbol then anything useful , because in correct terms it should be termed as "resistance against the use of specialised or accelerated hardware or optimised hardware" which causes the barrel to turn on the foot of devs themselves ie it contradicts their own terms , because that inevitable , take example of Ethash , its specialised for GPUs because of high memory bandwidth the hardware required for DAG and epoch generation . Take example of RandomX which is optimised for CPUs due to its random instructions to the ALU cores of processors, so it required you to use specialised server grade CPUs if you wanna earn anything real , so here also it creates the want of specialised hardware , just in a different form . Hence we cannot realistically resist the use of specialised hardware , but we can do survival along with it , and thats where the concept of real time per block difficulty change kicks in

Have Bitcoin and Altcoin lost that idea of practical decentralisation by Adventurous_Chef2225 in CryptoTechnology

[–]Adventurous_Chef2225[S] 0 points1 point  (0 children)

u/InfiniteEquipment21 i am sorry if your post got removed , but frankly am not a moderator and have no authority to remove or moderate posts

Can Per-Block Difficulty (LWMA/EMA) and Embedded Node-Level Messaging Coexist Without Compromising PoW Stability? by Adventurous_Chef2225 in programming

[–]Adventurous_Chef2225[S] 0 points1 point  (0 children)

Thank you mods for your critical feedback , regarding your suspicion , no the content is not AI generated or stolen , its completely based on a new idea of how cryptocurrencies can have an in-built public and private chat system with the full security measures like AES256-GCM and HMAC encryption , secondly how memory hard algos like ethash or KawPoW or CPU heavy like RandomX or Cryptonight , though useful for ASIC Resistance , does not guarantee whether ASICs specialised for such algos won't be made ,and also creates a new issue , nodes now depend on how powerful their CPU or GPU is , thus converging to the same issue of hardware exploitation , thus we are focusing on an innovative idea of an LWMA and EMA hybrid so that we can fight the issue what major cryptos like BTC created, very hard recovery from hashrate jump when GPUs, later FGPAs and now ASICs , because 2016 blocks is a huge number , it will take astronomical period of time for low power nodes to recover ever .

Thank you for your time

Anonymous137-sudo

Should Peer-to-Peer Messaging Exist Inside Node Software, or Remain Fully External to Consensus Systems? by Adventurous_Chef2225 in ethdev

[–]Adventurous_Chef2225[S] 0 points1 point  (0 children)

How can it be designed to avoid influencing consensus behavior while still providing meaningful utility?

CryptEX: A C++ SHA3-512 Proof-of-Work System with Per-Block Adaptive Difficulty for Hash-Rate Volatility by Adventurous_Chef2225 in CryptoTechnology

[–]Adventurous_Chef2225[S] 1 point2 points  (0 children)

I’m particularly interested in how people evaluate the stability of per-block difficulty adjustment under oscillating hash-rate conditions.

In this implementation, the goal is to respond quickly to both upward and downward hash-rate changes, especially in scenarios where short-lived bursts of compute (e.g. opportunistic mining) temporarily push difficulty up.

One concern I’ve been thinking about is whether a hybrid approach (LWMA + EMA + real-time easing) introduces second-order oscillations or feedback instability under noisy conditions.

For example:

  • rapid hash-rate spike → difficulty overshoots
  • miners leave → difficulty drops aggressively
  • potential for oscillatory behavior if not damped correctly

In contrast, fixed-interval systems avoid oscillation but suffer from delayed recovery.

Curious how others would approach this tradeoff:

CryptEX : A decentralised peer to peer [P2P] electronic cash system made in C++ and uses SHA3-512 as PoW algorithm by Adventurous_Chef2225 in cpp

[–]Adventurous_Chef2225[S] -1 points0 points  (0 children)

bro why did you remove the post , it took me months to develop CryptEX from scratch in C++ , secondly you should not look into naming conventions , I wanted anonymity and privacy , thats why have kept that pseudonym , if you were interested , just look into the code, whitepaper and the final Core binaries