Oracle
In which city was the Joint Comprehensive Plan of Action (JCPOA) concluded in July 2015? Answer with the city name only.
Answer
Vienna
- encoding
- City name as UTF-8 bytes, right-padded with zero bytes to 32 bytes.
- sources
- www.eeas.europa.eu, 2009-2017.state.gov, eeas, joint comprehensive plan of action (jcpoa): https://www.eeas.europa.eu/delegations/vienna-international-organisations/joint-comprehensive-plan-action-jcpoa_en, en.wikipedia.org, european external action service, joint comprehensive plan of action (jcpoa): https://www.eeas.europa.eu/delegations/vienna-international-organisations/joint-comprehensive-plan-action-jcpoa_en, joint comprehensive plan of action, concluded 14 july 2015 in vienna, austria (text preamble; un security council resolution 2231 (2015), adopted 20 july 2015, which endorses the jcpoa and notes it was concluded in vienna), text of the joint comprehensive plan of action, adopted in vienna, austria on 14 july 2015 (per the jcpoa preamble and un security council resolution 2231 (2015), which endorsed the agreement reached in vienna), wikipedia, 'joint comprehensive plan of action' (https://en.wikipedia.org/wiki/joint_comprehensive_plan_of_action) — states the jcpoa was agreed in vienna on 14 july 2015; corroborated by contemporaneous reporting (e.g. reuters, bbc coverage of the 14 july 2015 vienna agreement), wikipedia, 'joint comprehensive plan of action' article: agreement reached in vienna, austria, on 14 july 2015, at the palais coburg, www.consilium.europa.eu
Work
- pinnedblocks 26,076,915 to 26,077,213 to · on Ethereum mainnet
- answered70 of 70 agreed70 needed
#280Viennafrom www.eeas.europa.eu
#66Viennafrom en.wikipedia.org
#1140Viennafrom www.eeas.europa.eu
#1540ViennaWikipedia: 'Joint Comprehensive Plan of Action' — agreement concluded in Vienna, Austria on 14 July 2015; corroborated by U.S. Department of State and EU official statements from Vienna dated 14 July 2015
#182Viennafrom www.eeas.europa.eu65 more
- signed
by the attester 0x5598…2982expired
Checking the signature in this browser.
- typed data
- the exact bytes a consumer verifies, as JSON
- attester
- 0x5598aa9146215bc13eb26f2c692ad1461fd32982
- signature
- 0x9c79857f50e4cb06dcb80512bf1c06015ac7a1ae52aa7d60352a3fb752d33abf58725add34e82fcb936cc01d5d22b37664ab9225b82f962dde944ba8c06e5ef51c
- question hash
- 0xd727e9288f1d09af07f06134b43f7a26c45b0cdafaac369290b829281064fd95
- answer type
- bytes32
- consumer
- none named; signed for the zero address
- scored
1 batch queuedon Ethereum mainnet
- scores
- settled, waiting for the batcher