synthetix VS pfatt

For this new contract I've chosen to use the logic of Synthetix's StakingRewards for ERC20 staking which allows the distribution of a fixed amount of ERC20 tokens in a fixed period, with dynamic APRs that depend on how many ERC721 tokens are staked in the contract at each given point in time.

Yea. I wonder if buying a tokenised synthetic stock then would be the same eg: https://synthetix.io/

Visit https://synthetix.io then click on Staking takes you to

Synthetix has been running a bucket shop for a long time. They added stocks through Kwenta but got spooked and removed them.

https://synthetix.io/

Docs for Synthetix is unfortunately the code repo itself, starting with interface here

Looking through the Etherscan transactions for Serum and Jump Trading, I came across a new name - Synthetix.

I came across a new name from this list- Synthetix (website link)

Derivatives Marketplace - it could be something like what https://aperture.finance/ and https://www.mirror.finance/ had built before on the TERRA chain (currently on AVAX and coming soon to SOL) where you can buy STOCK DERIVATIVES or something like what https://synthetix.io/ does.

you guys are not up to date, check out synthetix.io, a lot of synthetics exist on the blockchain with pegged tokens. Obviously a true GME token backed by GME can exist and will be your tokens but it won't stop people from trading GME pegged tokens in a synthetic manner preventing price discovery

SNX, the token staked in the Synthetix system to produce synthetic assets;

See https://github.com/MonkWho/pfatt/blob/faa80d09f9c00e4a67bc3cacf2eab5a1631ec3f9/bin/pfatt.sh#L142-L151https://github.com/MonkWho/pfatt/blob/supplicant/bin/pfatt.sh .

I read through the PFATT Guide by MonkWho, but this setup was different. Setting up PFSense as a man in the middle to the gateway. I only have 2 Ethernet ports on my PFSense box, so this physical setup wouldn't work too well. I couldn't find mention of the supplicant method anywhere.

pfSense/OPNsense: https://github.com/MonkWho/pfatt

The bypass methods you are referring to were for prior models of the att router. My understanding is your model is not compatible. See the GitHub repo.

For ATT there is a wonky workaround for their gateway (used it for a while, not sure if it was me or pfatt but it reduced speeds): https://github.com/MonkWho/pfatt

I then used this pfatt.sh script and followed the instructions here: https://github.com/MonkWho/pfatt/tree/supplicant

Word of advice... Don't bother yourself with supplicant mode. It supposedly broke around 2.45. spent many of hours trying to get it to work again but it was a no go. Also ng_etf should be preloaded so you shouldn't have to bother with that. See the defacto replacement GitHub for this and other issues.