Answers Pectra FAQ questions

docs/wiki/pectra-faq.md

@@ -12,7 +12,7 @@ Overall
 #### **Q:** What is Prague/Electra?
 **A:** Prague and Electra are the names of the upcoming Ethereum hard fork. The included EIPs can be found [here](https://eips.ethereum.org/EIPS/eip-7600). Prague is the name of the fork on the execution client side, and Electra is the upgrade name on the consensus layer client side. 
 
-## Users/Devs
+Users/Devs
 ---
 **FAQ**:
 #### **Q:** What is EIP-7702/Account abstraction?
@@ -34,12 +34,15 @@ As a smart contract developer, you should know that after Prague the majority of
 As a security engineer / auditor, you must be aware that the previous assumption that a frame cannot be reentered when `msg.sender == tx.origin` no longer holds. This means the check is no longer suitable for reentrancy guards or flash loan protection.
 
 #### **Q:** What does the EIP-2537 BLS precompile add in pectra?
+EIP-2537 Adds operation on BLS12-381 curve as a precompile to Ethereum. BLS12-381 precompile enables efficient BLS signature verification. This is useful for applications where multiple signatures need to be verified, such as proof checking systems. 
 
 #### **Q:** How can I use the `BLOCKHASH` OPCODE?
+The last 8192 blockhash are now stored and available for access in the `BLOCKHASH` system contract. The `BLOCKHASH` opcode semantics remains the same as before, just that the block number can now be specified in big-endian encoding. The blockhash system contract can also be called via the ethCall RPC method, with the block number in question being passed as calldata. 
 
 #### **Q:** What are system contracts?
+System contracts are interfaces defined as contracts, which are essential for certain Ethereum functions to occur. The contract approach is used instead of each client implementing the logic in order to simplify maintenance as well as allow for upgrades in the future with minimal overhead.
 
-## Stakers
+Stakers
 ---
 **FAQ**:
 #### **Q:** What changes about deposits?