nucypher
nucypher copied to clipboard
nucypher
Threshold Access Control (TACo) runtimes for the Threshold Network
Enabling support for multiple intervals to collect metrics (large interval for those metrics that requires a connection with a web3 provider as Infura and short interval for those metrics only...
Questions: - Should there be a default static value used by the node? - Can "freshness" be set as a ritual level parameter? - Can it be a per-ciphertext configurable...
Related to discussion in #3140 raised by @piotr-roslaniec - https://github.com/nucypher/nucypher/pull/3140#discussion_r1230923557. What sort of limits should we put on `CompoundAccessControlConditions`. ``` @[piotr-roslaniec](https://github.com/piotr-roslaniec) piotr-roslaniec [21 minutes ago] Not specific to this PR:...
Initially it was introduced as a performance optimization to prevent sending the metadata to another node if both node have matching fleet states. But how often does that really happen...
What is the one canonical place for de/serialization of protocol objects in the decrypt flow? Currently we have: `conditions = json.dumps(conditions).encode() # aad` ...assuming that the objects are list-ish (`LingoList`...
**Describe the Bug** ``` {"jsonrpc":"2.0","id":1,"result":{"accessList":[],"blockHash":"0x6890839166764a06cfaf0e8ff5b1cb5446e9ca544920f59c33f853112ac57b63","blockNumber":"0x2b07e13","chainId":"0x13881","from":"0x890069745e9497c6f99db68c4588dec5669f3d3e","gas":"0x42fe9","gasPrice":"0x69cde061","hash":"0x921598a08ad719e22ce0be0c1faf3959cacdf952082bee37eb52cc8917b53fd6","input":"0x8cf95061000000000000000000000000000000000000000000000000000000000000000700000000000000000000000000000000000000000000000000000000000000a0ac9388d42b7fdd3245b24f65ef888b4cdc7a249437b6003b8ebdf04911bb78187cb171e6aa0e8bbafd72ab9f5e88e43c0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002e0000000000000000000000000000000000000000000000000000000000000020868000000000000000200000000000000ac9388d42b7fdd3245b24f65ef888b4cdc7a249437b6003b8ebdf04911bb78187cb171e6aa0e8bbafd72ab9f5e88e43caf78ad7f65d0b95f99d1c06ef667682750cb016f96620930a9486e8e09608c0772919ada5d4e4531c0210fd1c3bb892928010000000000000300000000000000a3657a54f55d767120c38b3399ca0b3b72186570d9310f1174f34941835db894c61cd1c6fa218a51b7b637a64decc11d08e752c554e2e1ca877ee071a3cef39514c2e50409b559fa07d924637b78c1171cd202de83868f756d1f4eaac390605a807bb6b35ded28ad167fc72705b46e6c0d8463b6b2856cd97525d3505e67f0ad5f8d8df242b8c5f7940271cf2fb22e1c156dfd51d07f60e1c2c0b7dbde3504a6eac2cba1fbf6ab27874ffa1fe7b8e92c7b60f3ada3c6e1712573665296471cdeb3d33df4aa7265bd147fd20709da2b276243b0c0739fff3c7bd246a1d2b3377462c25165578d7f826aee36f33f2d87aa0cf80328d697648d16506b06743ef45e339c69d9a5f1d60636946f1bd809f3aa2321cda8cfcb5c81628a04ba513a19dd600000000000000085341825e14d52cb0081491b621e181844a1a35cd5386c974c15bebb051a61d161bdc76595e716d3fa0587eb861197c30ec2b75a1a1d5715a57300130d7220b24b8f11f532243cb48ef7c9ed48464ca83842835b5dc2e9c614ee7857767fcffc000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002a5453536b00020000c420d7da6003a906200e7338f5e3bad27576b5a9ab339bc05ff10604a4b93d76546600000000000000000000000000000000000000000000","maxFeePerGas":"0x69cde070","maxPriorityFeePerGas":"0x69cde052","nonce":"0x84","r":"0x65e4cc44933e65507927db93d493cad20ea651cc49e47d720936296cca18130c","s":"0xb96a27dfbecc030edd14a01fe4d4cb052163eb00cdcc32299798ab4cf75d3ee","to":"0x530608219a8a671fd183534b17e2a2ce09e782a4","transactionIndex":"0x6","type":"0x2","v":"0x0","value":"0x0"}} ``` **To Reproduce** Steps to reproduce the behavior **Traceback or Screenshots (Optional)** If applicable, add the full error message / Traceback or upload screenshots to...
See conversation here - https://github.com/nucypher/nucypher/pull/3393#discussion_r1456308853
Inspired by #1676 -- Currently we employ environment variables and plaintext inputs for collecting keying passphrases. Is it possible to improve on this practice further by also accepting a filepath...