Qora Web

website
<!DOCTYPE html>
<html>
<head>
<link rel="shortcut icon" href="/i/2139.png">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>/i2139</title>
<style>
* {
  box-sizing: border-box;
}

body {
  font-family: Arial, Helvetica, sans-serif;
  font-size: 28px;
  margin: 0;

}

body a {
  text-decoration: none;
  color: #2471A3;
}

body a:hover {
  font-weight: bold;
  color: #8871A3;
}
</style>

</head>
<body bgcolor="#BAADBE" topmargin="0" leftmargin="0" rightmargin="0" bottommargin="0" marginwidth="0" marginheight="0">

<img border="0" alt="/i/2139.png" src="/i/2139.png" width="100%" height="20" align="top">
<p id="whatluck" align="center"></p>

<script>
let luck = "";
const d = new Date();
const y = d.getFullYear();
const m = 1+d.getMonth();
const x = d.getDate();
const r = d.getTime() + 168;
for (let s = 1; s < 3; s++) {
let z = 999*y*m*x+9*s*(s+1)*(y+m+x)+s+r; 

let a = 9776+z%8;
let a2 = 9800+(z+m)%12;
let a3 = 8528+(z+x+m)%15;
let a4 = 126976+(z+x+y)%42; 
let b = z%10000;
let b2 = 126976+(z+m)%42;
let b3 = 126976+(z+m+y)%42;
let b4 = 126976+(z+m+y+x)%42;
let b5 = 128000+(z+x)%61;
let b6 = 128512+(z+y+x)%56;
let c = (z+m*x+123)%40 + 20;
let d = c * 100;
let e = (z*3+m+x+y+321)%20 + 20;
let f = d + e; 
let sss = 1 + (s+r)%2;
let ss = 9792+(sss-1)*2;
luck += '<a href="/i'+f+'" title="good i'+f+' luck !"><img border="0" src="/i/'+f+'.png" height="25">'+' &#'+ss+';'+ '&#'+a+';'+'&#'+b5+';'+'&#'+a4+';'+'&#'+b2+';'+'&#'+b3+';'+'&#'+b4+';'+'<img border="0" src="/i/'+f+'.png" height="25"></a><br>';
}
document.getElementById("whatluck").innerHTML = luck;
</script>

<p align="center">
<i>"The reason I didn't use protocol buffers or boost serialization is because they looked too complex to make absolutely airtight and secure.  Their code is too large to read and be sure that there's no way to form an input that would do something unexpected.<br><br>
I hate reinventing the wheel and only resorted to writing my own serialization routines reluctantly.  The serialization format we have is as dead simple and flat as possible.  There is no extra freedom in the way the input stream is formed.  At each point, the next field in the data structure is expected.  The only choices given are those that the receiver is expecting.  There is versioning so upgrades are possible."</i>  Satoshi Nakamoto
<font size="3"><a href="https://bitcointalk.org/index.php?topic=632.msg7090#msg7090" title="bitcointalk.org"> BTT August 02, 2010</a> </font>
<br><br>
<font size="2">Owner Log Records for :</font><br>
<img alt="" src="/i/2139.png" width="25"><b> i/2139.png</b>
<img alt="" src="/i/2139.png" width="25"> <br>
Linked 
		<a 
			href="https://opensea.io/item/ethereum/0x495f947276749ce646f68ac8c248420045cb7b5e/796638993731848468553700001337130722622321311759604289543104076842260234241"
			target="_top" title="i/2139.png OpenSea Qora2 NFT">
OpenSea NFT
		</a>
<br>
Linked Qora Name :<br><a href="/ugolnyekopi" target="_top" title="Qora Name : /ugolnyekopi">/ugolnyekopi</a>
on <a href="/i" target="_top" title="Qora Name : /i World Map">/i World Map</a><br>
Owner :<br><a href="/okchai" target="_top" title="Qora Name : /okchai">Okchai</a> since June 2023
<br><br>
 <a href="/aitway" title="aitway's dweb">AITWAY.COM</a> <b>50%</b> off for OpenSea Qora & Qora2  <a href="/opensea/1" title="Qora and Qora2 NFT by okchai">NFT</a> holders
<br>
<br><a href="/i2138" title="/i2138">{ -</a> [] <a href="/i2220" title="/i2220">- }</a>
</p>
<img border="0" alt="/i/2139.png" src="/i/2139.png" width="100%" height="20" align="absbottom">
<iframe width="100%" height="550" frameborder="0" src="/footer" name="foot" border="0"></iframe>
</body>

</html>
website
